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
Change the recommended Apache Port from: port 80 to port 81.
Stoping the Apache solved this issue for me, using the command-line:
sudo apachectl stop
Also make sure you're not launching an older version of MAMP. This happened to me when using spotlight to find MAMP. When the app upgrades, it keeps older copies around in your Applications folder.
I had this problem and it turned out that a .txt file that was not a vhosts file had somehow been saved to my sites-available
folder that Apache was automatically including, and expected every file to be a vhosts file.
I had the same problem. After a lot of frustration about not having a descriptive error message, I realized I could check the "All messages" log under Applications/Tools/System messages (or some similar path, as I just translated from my language here). There I found the explanation, which in my case meant that a library link was broken (probably due to the uninstallation of postgres). I fixed this by recreating the link. In my case it meant I had to run the following command in the terminal:
sudo ln -s /usr/lib/libpq.5.3.dylib /usr/lib/libpq.5.dylib
and now it works!
Command line helps for this issue. like the below,
/Applications/MAMP/Library/bin/apachectl start
/Applications/MAMP/Library/bin/apachectl stop