Forum of Apache users Forum Index Forum of Apache users
Discussions of software for tuning the Apache web servers
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Apache2 on Leopard stopped serving virtual hosts

 
Post new topic   Reply to topic    Forum of Apache users Forum Index -> General questions
View previous topic :: View next topic  
Author Message
ken_ww



Joined: 29 Dec 2009
Posts: 2

PostPosted: Tue Dec 29, 2009 7:09 pm    Post subject: Apache2 on Leopard stopped serving virtual hosts Reply with quote

My MacOS X Leopard server was serving up 4 virtualhost sites without problem until just today, when it started simply responding with the Apache server placeholder default page. I have made no changes in my httpd.conf file or any of the extras or other files included directly or indirectly by httpd.conf for months, so I don't know how this could happen.

I verified that these files are all as I last left them and find no changes at all. Accordingly, httpd should be sending the correct html files for each of the virtualhosts (www.kingkrill.com, www.whitmore-family.net, www.alaska43.org and www.top-ocean.biz).

I've double-checked the IP's for each of the domains, as shown by dyndns updater, against the actual WAN IP of the firewall/router, and they all match.

I see no reason why the default page is being served.
Help!!!
Back to top
View user's profile Send private message
ken_ww



Joined: 29 Dec 2009
Posts: 2

PostPosted: Tue Dec 29, 2009 7:36 pm    Post subject: Re: Apache2 on Leopard stopped serving virtual hosts Reply with quote

httpd -V shows version is 2.2.13 (Unix), which is contrary to what Apache's site indicates as being included in MacOS Leopard.

httpd -S shows the default server is www.kingkrill.com, but the default page being served is not the www.kingkrill.com home page!!! How could this be?

Also, httpd -S shows all 4 virtual hosts set up as namevhosts on the correct port number and with the correct .conf file paths.

Could it be that somehow httpd itself has been damaged? If so, what's the minimalist approach to restoring it?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Forum of Apache users Forum Index -> General questions All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

Anti Bot Question MOD - phpBB MOD against Spam Bots