Note: since this blog post was written, it has received about 250 hits a month by itself from random google searches. If it does not solve your issue, please please write up your solution on your own wordpress blog and pop a link in the comments, or just write it up here.
I’ve encountered this one a fair few times.
The problem, for me, is that this is a misleading error message. It makes you think about SSL, about something to do with caching, about anything, in fact, other than what the problem is. As such, I’ve spent frustrating HOURS sitting around googling reading about changing apache’s ssl stuff to this and that and the other thing, when none of them are the answer.
Okay, the problem is this: you haven’t configured DNS correctly. That simple. Your machine is, for some reason, unable to resolve your machine name correctly.
The solution here is for FreeBSD, but now you’ve got an idea of what the problem actually seems to be you might be able to fix it.
first, edit /etc/hosts and enter your ip address, machine name and domain name.
For me, because I’m privately addressed and have no domain name for the machine, I did this underneath the line about localhost:
192.168.77.108 pigeon pigeon.my.domain
Then save that sucker.
Next, use the hostname command to change your host name:
Great, almost there.
To not have to type the above command in every stinking time the machine reboots, enter:
Finally, change the line that reads something like:
in /usr/local/etc/apache22/httpd.conf to read something like
Now do an apachectl restart and bob’s your mother’s brother, everything’s tickety boo!