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
I have been going through all Stackoverflow posts, but no luck. Finally, I came across this: https://www.speakinginbytes.com/2013/02/mamp-problems/
Sometimes Apache is set through MAMP to open a particular folder and that folder no longer exists. If you simple go to MAMP and change that setting through the preferences button you should be able to fix it.
That did the trick for me. Hopefully it will help someone else!
1) Quit MAMP
2) Use the command-line to run:
$ sudo apachectl restart
3) Open MAMP and start Apache
4) Apache should start this time with any luck
My situation was that when I used the command-line to run:
$ sudo apachectl stop
nothing changed. And when I used the command-line to run:
$ sudo apachectl start
I received the message
httpd (pid 600) already running
I tried restart instead and it worked.
To fix this particular issue, I reinstalled PostgreSQL and the apache build that came with it, then I installed MAMP again and MAMP worked fine.
In my case was a wrong ssl certificate on an vhost. To test, just temporarily deactivate ssl from all your ssl vhost and see if it starts. NOTE: even if the ssl vhost are not checked.