You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Lion Server fail

Ok, so I installed Lion Server this morning and mostly had it configured using a new SSL cert from GoDaddy. Quite suddenly, though, all web-based access (wiki, profile manager, web server, etc) stopped working with a "safari can't connect to the server" error in Safari. Looking in the System Log, I see a rapidly advance series of the following error:


Jul 21 12:07:52 sidhome org.apache.httpd[5802]: [Thu Jul 21 12:07:52 2011] [warn] _default_ VirtualHost overlap on port 443, the first has precedence

Jul 21 12:07:52 sidhome com.apple.launchd[1] (org.apache.httpd[5802]): Exited with code: 1

Jul 21 12:07:52 sidhome com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds


Can someone give me some pointers at what is the root cause of this? I know have a $50 log filler.

OS X Lion Server-OTHER, Mac OS X (10.7)

Posted on Jul 21, 2011 12:14 PM

Reply
27 replies

Jul 23, 2011 7:02 AM in response to craigfromlivermore

Digging into the log files, I find lots of "/var/empty" reference problems. This DocumentRoot appears to be hard coded into numerous of the .conf files that are auto-generated by the sever configuration process. However, I can't find where in the Server program to reset this. So my conclusion: LION SERVER IS NOT READY FOR PRIME TIME. I will wait out the next (ie first) update from Apple.

Aug 1, 2011 5:57 AM in response to Mountainboy

Hi


I'm having similar issues. Caldav, CardDav and VPN seem to work without a problem (both locally and over the Internet). It seems to be the services such as Profile manager portal (works locally, not over the Internet) and Webdav (doesn't work at all) are having the biggest issues, and my iphone is reporting it can't find the server both locally and over the Internet.


Like others, DNS, router configuration, etc look to be fine.


This is my 3rd rebuild of lion server as I thought I'd messed things up but I'm now thinking its not me (btw this is my first venture into mac server). On my 2nd build after disabling ssl to get webdav working apache was reporting no crt file found.


I am also using a Self Signed Cert. I'm using lion server as a home server so a paid for Cert would just be too expensive and as Mountainboy said it shouldn't make a difference, especially when the other services seem to work and use the Self Signed Cert.


Any help would be very much appreciated.

Aug 25, 2011 10:31 PM in response to craigfromlivermore

I ran into a very similar problem on my XServe running Server 10.6.8 with the latest updates. I deleted the default certificate, which had expired, and created a new self-signed certificate. I did not have any web services using, SSL -- I was attempting to use SSL to have managed clients connect to the server, but ran into problems and then disabled SSL directory connections. After that, all web services became inaccessible. I received the "safari can't connect to the server" error. I noticed that in Server Admin I was able to read my Web logs when Web services were stopped, but when it was running the logs disappeared.


I disabled each site in Server Admin, restarted Web services, and brought each virtual host up one by one. That fixed it.


I'm assuming that there is a problem linking SSL certificates and the httpd.config/virtual hosts file, both in the latest 10.6.8 and 10.7.

Sep 7, 2011 11:24 AM in response to craigfromlivermore

I had the same thing happening to me earlier today. Not following any good practice I haven't tested between changes so I can't tell exactly what is causing this. Either a change of hostname or a change of cert.


It seems that server.app has messed up the Apache config by assigning the same port to multiple .conf files in this directory. Not only this but it also removed most of the important stuff from those files.


In any case, here's what I did to fix (need to do some CLI work).


*Caution* - if you have other sites live on the server, it may introduce further problems (do the backups and re-install whatever config needed. This was done on a fresh-ish install with only profile manager and OpenDirectory running.


1. Fire up terminal.app

2. cd /etc/apache2/sites

3. sudo mkdir backup (can be skipped if you feel courageous)

4. sudo mv 0000* backup/

5. Back in server app, Under Hardware -> $your_server_name -> Settings -> SSL certificate, re apply the cert you want. This should re-populate the 0000* files you moved at #4

6. Back once more in terminal, run this : sudo /usr/sbin/apachectl restart


The error should go away and web sites for server should be back to normal.


Hope this helps.

Marc/

Sep 8, 2011 12:48 AM in response to mobibaud

A simpler solution which might work as well:


  1. Open Server.app
  2. Turn off all services
  3. Go to Hardware => Your server => Settings => SSL Certificate and make sure the correct certificate is set
  4. Go to Hardware => Your server => Network => Change hostname to what it already is (going through the process will do some rebuilding of the httpd.conf and restart apache properly.
  5. Turn on one service at the time, give the server time to fully start one service (you'll see the spinning wheel at the bottom right) before you go on stating another one.
  6. Check that SSL certificate is still set correctly.

Sep 14, 2011 11:43 AM in response to burti

I am having the same exact problems and all these solutions people post are temporary fixes. Once you apply a fix, it works for like 1 minute until Lion Server breaks itself again. I've done multiple clean installs, installed Lion Server on multiple hardware but nothing seems to work.


Most of the time, Apple products just work and they are simple. In this case, Lion Server was a nightmare.

Sep 14, 2011 12:18 PM in response to Laurel School

Laurel, this is a problem within Apache config files. Granted I've seen Lion Server mess them up completely but I would be quite surprised if they get overwritten without any action.


Once you've fixed and confirmed profile manager works, do this in terminal :


stat -x /etc/apache2/sites/0000*


When profile manager breaks again, do the same and compare the modify timestamp on the file. If the timestamps are the same, the issue is likely to be something different.

Marc/

Lion Server fail

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.