Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ideas why my VHost suddenly stopped working???

Status
Not open for further replies.

BobMCT

IS-IT--Management
Sep 11, 2000
756
0
0
US
I am reasonably familiar with apache having run dev and production servers for over a decade. Usually things just run and run even when adding new virtual hosts, etc.

I'm hoping some fresh eyes and brains on this will provide what I may be overlooking.

The other day I was trying to reconfigure one of the existing virtual hosts to be secured (SSL) and ran into problem with SSL errors. Somehow, in my editing I must have changed something that now causes every site request to go to the default site. The common error in the log is that apache cannot find my project in directory whatever which is always referring to the default site's documentroot directory. Of course, cause the prog is NOT in that directory.

So, what must I have changed to disassociate all my virtual host directories? Which hopefully simple directive must I be missing. I know its relative to vhost vs. default site 'cause which ever site I place first or modify to _default_ is the one which works.

When I run httpd -S it displays all my virtual hosts along with their correct document root dirs.

I even restored my configs from backup from days before any changes were made and still no deal.

I am running Ubuntu Server 8.04 LTS and XAMPP 1.7.3a installed in the /opt/lampp directory. My config files are in the standard places for lampp (/opt/lampp/etc and /opt/lampp/etc/sites-enabled)

I'm kind of stumped and am hoping that some of you members have run into this before and can provide some ideas/suggestions.

Any info at this point is GREATLY appreciated.

Thank you...[nosmiley]
 
I don't want to state the obvious, but did you check both httpd.conf and httpsd.conf for any accidental changes? Both can have vhost configurations in them.
 
I hear you and I realize the obvious but that's ok because most often that's the issue. My frantic request was out of frustration and since then I've restored my prior conf files from a backup and the sites are back online albeit without the changes I was attempting to make.

I am doing a diff/visual compare of the old and the new and first pass don't see anything obvious. However, I will most likely post my finding when and IF I can accurately determine the cause 'cause I'm sure there are others who will be in the same boat I am in.

Thanks...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top