Lion Server and Virtual Hosts

Hi,

I am having problems with this two, is always necesary to modify the .conf files?

Apple said that "Adds the ability to set up multiple websites with different host names on the same IP address.", but i don't found any instructions to do that!!!!

Hi,

I found a very simple solution without modifying httpd.conf.

The only file that you have to modify is hosts in the etc folder (/privacy/etc)

Add the following in a new line

127.0.0.1 www.yoursite.com

Then goto web in the server app, add the a new website with the + sign. Write www.yoursite.com, any in the ip and select a folder, for me only worked with a folder inside library/server/web/data/sites/yourfolder

inside of "yourfolder" put a file default.html

It's really works! Try it!

No other problem occur, no "error reading settings"

You can add many site repeating this procedure!

Can 127.0.0.1 www.yoursite.com then be accessed from the internet? I thought 127.0.0.1 was the localhost.

I just had the same thing happen on 10.8.4.

Server App overwrote all of my virtual port 80 domains with 443 versions.

I had several clients call me to tell me their sites were down and after hupping the daemon and rebooting I realized that the server wasn't responding on port 80 for any of our sites because they were all overwritten with 443 versions. No changes have been made to the server in months.

My situation:

OS 10.8.4

server mac mini server 8GB RAM, 2ghz intel core i7

1. My self assigned certificates are or were expiring.

Hard to tell since I renewed it a month or so ago, but still receive daily errors from the machine saying they need to be renewed.

2. I was looking at server app to see if i had any other certificates expiring. I DID NOT make any changes to certificates, or server app, or apache, I did not renew any certificates

I'd like to note, if any Apple folks see this, that in addition to overwriting all of my port 80 sites to 443 there are several other issues with the apache portion of server app:

1. you can not correctly write custom errors to the .conf file. It only writes for 403, you have to manually add 404 and 500

2. you cannot use any redirect to a php file or perl file for example for error handling, it only let's you type .html files into the server app interface

3. if you manually enter your conf files, which i do because the server app is broken and I need custom error handling, then when you save ANY site, all virtual sites get redundant error lines written over and over, sometimes hundreds or even thousands of times. I've seen apache conf files grow to be several megs with the redundant lines.

4. I've also noticed that the http daemon has stuck process extremely frequently. I've never seen this in any verson of OS X server since 10.1, I've used them all. But in 10.8 I see runaway apache processes every day that take up 100% of cpu and run forever until you manuall kill -9 them.

Thankfully I had backed up the "sites" directory previously and was able to recover fairly quickly and gracefully.

I've done further confirmation through researching various log files and I find in WebConfig.log where it takes all of the 0000_any_80_ files and rewrites them all to 0000_any_443_ files.

Clearly I couldn't have done this because the server app only allows you to edit one site at a time but I see in this log where it rewrites them all to 443.

So they question is how do we track how and why this happened, but there is also no indication in the log of what user or what command executed to make this happen.