Apache not starting in MAMP (but MySQL working) in OSX

Question

I\'ve had MAMP working for a few months and recently installed PostgreSQL. It recommended installing Apache as well, which I did to make sure PostgreSQL worked. I then uninsta

Answer 1

Maybe its because the original apache is on. Have you tried to see the status ? You can try this command to stop it "apachectl status" and then restart mamp and see if it works.

Answer 2

I had a similar problem and could solve it by starting on the command line the apachectl included in MAMP:

$ /Applications/MAMP/Library/bin/apachectl start

which would yield

Syntax error on line 427 of /Applications/MAMP/conf/apache/httpd.conf:
Invalid command '\xef\xbf\xbc#AllowOverride', perhaps misspelled or defined by a module not included in the server configuration

This error message was nowhere else, not in any log file or system console. (Turns out I had copied a line from a documentation file which had copied some special characters that were not intended for my system - how easy to find is that!)

This is for MAMP 2.0.1, maybe it's handled better in newer versions.

Answer 3

I know this is old but in case someone else comes across this. I had a typo in my Virtual Host file (/Applications/MAMP/conf/apache/extra/httpd-vhosts.conf) that was causing Apache not to start. It wasn't until I manually tried to start MAMP's version of Apache from the command line (/Applications/MAMP/bin/startApache.sh) that I saw the error and was able to fix it.

Answer 4

If your htdocs (or equivalent) folder is stored on external storage, you may need to connect to it (in finder, or using cmd + K) before apache will start.

Answer 5

If it has at one point been working fine then I guess something else on your network is currently using the same port for something else.

I had this problem too: in my case I had changed the default MAMP Apache port from 8888 to 80. It worked fine until I installed a web server on another machine on my network and tweaked /etc/hosts on my local machine to include the new server. This meant that port 80 was already in use and MAMP's Apache couldn't start.

The solution was to either stop the second web server on my network, or revert MAMP back to 8888. Both approaches worked fine.

Answer 6

For those of you upgrading to Yosemite there seems to be a bug which I don't really understand but its easily fixed as posted on their twitter account.

Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in '/Applications/MAMP/Library/bin' into “_envvars” (@mamp_en)