Multiple websites

You, sir, are a lifesaver.

This is very helpful as I'm basically a rookie at all this. Of course, I receive a "permission denied" when I enter the full command you gave. That's a bad sign when utilizing the "sudo" command, no?

Wow, glad to see that someone found a solution!

i will try that later today!

Thanks!

And if you have SSL enabled the solution is

sudo echo NameVirtualHost\ \*:443 > /etc/apache2/sites/00000_MoreTestingRequired.conf

instead of

sudo echo NameVirtualHost\ \*:80 > /etc/apache2/sites/00000_MoreTestingRequired.conf

issue a "sudo su",

type your password

then run the command

echo NameVirtualHost\ \*:80 > /etc/apache2/sites/00000_MoreTestingRequired.conf

or if you have SSL enabled run

echo NameVirtualHost\ \*:443 > /etc/apache2/sites/00000_MoreTestingRequired.conf

instead

i followed your step and it worked!

Thanks!

now the only things that don't work is trying to go to:

www.domain.com/postgres

www.domain.com/changepassword

i have sites that use MySQL and i would like to import them with postgre

If you also change it from Any IP to the one bound to the interface on the server it will work too. On a side note, anyone able to get the site to work with both HTTP and HTTPS?

Guys, it's alot easier than this.

THIS EDIT BELONGS IN YOUR httpd.conf FILE NOT AN INDIVDUAL WEBSITE .conf FILE

/etc/apache2/httpd.conf

Any where in the MAIN server configuration area (and for you techies out there) prefereably in the websharing portion find the area that resembles:

<IF DEFINE MACOSXSERVER>

blah blah

</IF DEFINE>

section,

just add this line on a new line in between the <IF DEFINE> </IF DEFINE> brackets:

NameVirtualHost *:80 (for non-SSL) (<--- don't add the parens)

NameVirtualHost *:443 (for SSL) (<--- don't add the parens)

That's it.

Then all of your virtual hosts should work. There is no need to add the *** MoreTestingRequired line.

Sorry for the double post...

Message was edited by: sbkeith

@sbkeith - the reason for breaking it out into a seperate file is to ensure that it doesn't get overwritten by the config tools, or whenever Apple releases a patch that blows away the 300+ line httpd.conf file.

The individual site configuration files are picked up by an include statement at the bottom of the httpd.conf file, so as long as the file placed in the sites directory begins with a string of five zeros then it will be read before the individual VirtualHost statements that relate to each virtual host.

Yes, I agree with you.

Wasn't bashing your response and if it appeared that way, I humbly apologize.

I always add this edit to the default.conf files to avoid such overwriting and thus far, have been successful.

SysAdmin preference I concede.

Also - a housekeeping note: Delete all the (IF DEFINE !MAC OSXSERVER> entries and comments (they are in the default .conf file anyway) and it won't be 300+ lines. A OS X Server will never be anything other than an OS X Server so these lines are pointless.

Alright, I've tried the suggestions here along with a lot of other things but I'm not getting this to work. Am I alone, or are there others for whom this doesn't work?

No matter what subdomain I go to (which have different document roots), I always get the "Welcome to Mac OSX Lion" page. Even a virtual-host that's set as a reverse proxy just continues to go to the welcome screen.

I've tried adding as a sites/ file named as suggested, also placing it in the httpd.conf.

Even adding new websites via Server.app doesn't appear to do anything.

This was an upgrade from an existing SLS installation.

I have not been able to get it to work, either. Same issue, similar situation (upgrade from SLS).

Dive into the "sites" folder and make sure your changes haven't been placed into a conf.prev file. Server.app likes to "clean" that directory.

If your sites are https:// Open "Server.app" go to the "Hardware" section click on "settings" Check that the sites have a SSL profile.

After much trial and error I think I have finally fixed it.

No, I've gone so far now as to disable all of the sites/ .conf files and try hard-coding the virtual host descriptions into the httpd.conf file and still no dice.

One interesting thing: With everything removed the log errors show it is looking for files in /var/empty, as you would expect. If I add in a very short, simple virtualhost for *:80 then I can specify a new DocumentRoot and it works as expected. But, if I add another virtualhost for my real hostname with a different document root, it continues to use the settings (and document root) of the *:80 vhost. If I remove the *:80 virtualhost it falls back to /var/empty.

That indicates to me that the virtualhost directives are being read, but somehow the hostname is being mangled such that the only vhost directive that will match it is *. Does anyone know how to print out the hostname that apache thinks it is operating under?