Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So, I upgraded my business server to Lion yesterday - BIG mistake. However I really want the WDE that comes with FileVault 2, so I'm trying to cope with all the fuzz. One thing that I can't figure out, however, is why the web service can't start when I add a domain name twice, but with different ports.

Here's what I do: 1. is added with an SSL certficiate (port 443). All is good, site can be accessed. 2. is added without SSL (port 80). Web service dies, can't start, and all my sites die instantly.

Any ideas?

OK, so I figured out the problem at least; whenever an SSL domain is added, also saves a redirect for the port 80 equivalent of the SSL domain, named 0000_any_80_example.com_shadow.conf. It must be the _shadow.conf that's crashing with the regular port 80 domain .conf.

When I realized this, I stopped the Web service, removed the shadow file, wrote a new "regular" .conf file which I then renamed to _shadow.conf, and turned on Web service... Only to see it be overwritten by the service. :(

Oh, well - problem solved with an easy workaround. I just saved the port 80 domain differently, so I did this:

Port 443:, additional domains: * Port 80:, additional domains: *,

Worked great, luckily. :)

I still would like a "real" solution, though. Any ideas?

share|improve this question
Any site that can be connected to using SSL usually has another option to be connected without. That's probably why it's giving you a problem. – rubixibuc Feb 16 '12 at 7:56
Yes, exactly. Is there no setting (in perhaps Apache) to disable this "feature"? – toooft Feb 16 '12 at 11:16

The creation of __shadow.conf files might not be stopped in Lion Server.

Apache can be stopped from loading these __shadow.conf configuration files by modifying /etc/apache2/httpd.conf.

There is a section at the bottom that looks like:

    Include /etc/apache2/sites/*.conf

You could change that to for eample (expand the list to match all tld's that your are hosting):

    Include /etc/apache2/sites/virtual_host_global.conf
    Include /etc/apache2/sites/*_.conf
    Include /etc/apache2/sites/*.nl.conf
    Include /etc/apache2/sites/*.com.conf
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.