Skip to content
MAMP PRO Documentation

Apache will not start

Another Apache process is running on the same port

Section titled “Another Apache process is running on the same port”

The most common reason Apache fails to start is that another httpd process is already using the same port. To check:

  1. Quit MAMP PRO.

  2. Open Activity Monitor (/Applications/Utilities/Activity Monitor).

  3. In the View menu, select All Processes.

  4. Type httpd into the search field in the top right.

    Activity Monitor - httpd

  5. Quit every httpd process listed in the results.

  6. Start MAMP PRO again.

  7. If Apache still does not start, check the log file for error messages.

Skype is using the same port

Section titled “Skype is using the same port”

Skype can occupy ports 80 or 443, which conflicts with Apache. Either quit Skype before starting the servers, or change the Apache ports in Settings › Server › Ports.

The Apache template file is damaged

Section titled “The Apache template file is damaged”

If you have manually edited the Apache template, a syntax error may prevent Apache from starting. Rename httpd.conf.temp to httpd.conf.temp.bak in ~/Library/Application Support/appsolute/MAMP PRO/templates — MAMP PRO will then regenerate a clean template on the next start.

A site has an invalid document root

Section titled “A site has an invalid document root”

Apache will refuse to start if a site’s document root points to a directory that does not exist. Verify that all sites in the Sites list have a valid document root.

← Apache