OS X Server: How/where is the server app changing the Apache configuration?

Posted on

OS X Server: How/where is the server app changing the Apache configuration? – Problems with loading a website are often blamed on the Internet connection, but even the most perfectly set up network cannot help if there is no service to reply at your destination. One of the most popular HTTP servers used for this task is Apache2. Much of Apache’s popularity can be attributed to its easy installation and use, but never the less it is possible to run into problems with even the easiest of the software. If you’ve encountered an issue loading your web page, follow these simple troubleshooting methods outlined in this guide to attempt to get your web server back up and working again. Below are some tips in manage your apache2 server when you find problem about apache-2.2, mac-osx, mac-osx-server, , .

When I view the “Websites” section in the OSX Server app, I am able to manage what appear to be virtual hosts. However, when I go to check Apache’s vhosts configuration, there doesn’t seem to be anything configured. Is there some kind of magic going on here, or are the changes made via the Server app affecting files somewhere else? Can anyone shed some light on how OS X manages the built in Apache installation?

Since you mention Server App, I assume your OS X is Mountain Lion. The actual apache config is at the following location


Virtual host config is in


You are probably looking at /private/etc/apache2/ or /etc/apache2/, which is not being used.

It’s worth mentioning that the configuration files for the default sites in macOS Server (HTTP, port 80, and HTTPS, port 443) are located here:


On my Mac mini, there are files for 80 and 443 but they are not used.

Leave a Reply

Your email address will not be published.