I have been running MAMP Pro 3.05 successfully in Yosemite up to DP4 on a partition that was a clean install of Yosemite.
I now have run the installer for DP5 over m
Sometimes, it's not always the envars
files that's the culprit. If you've been editing the vhost file at /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf
, a syntax error could cause MAMP's apache to not start without a warning.
In that case, you can run the following command and see if any errors are encountered.
sudo apachectl stop
I got MAMP v3.4 working.
I renamed "envars_" to "_envars" ... but that didn't work.
I had to also go into preferences, and hit the "Set Web & MySql ports to 80 & 3306" button!
Works!
The approved answer didn't work for me because the _envvars file was already there. I had to download the latest version of MAMP and install it and it worked.
MAMP Pro 3.0.7.3 should run fine on Yosemite, but after installing it on a brand new machine, I experienced the same problem.
In my case, the problem occurred because I had defined Additional Parameters for my virtual host that contained quotes. By default, Yosemite keyboard settings are set to convert straight quotes to smart quotes ("no-cache" became “no-cache”. Depending on font and font size, this may not be immediately obvious). This made Apache crash, even when the host was disabled.
To change this settings, go to System Preferences -> Keyboard. In the Text tab, uncheck Use smarts quotes and dashes.
I was running MAMP 3.0.5 on Mavericks. After upgrading Mavericks to El Capitan, I ran into the same issue. Mysql did start normally but Apache did not.
After renaming envvars
to _envvars
in the folder /Applications/MAMP/Library/bin
such as suggested for Yosemite, I was able to start Apache as before.
So, this fix works for El Capitan as well!
I didn't get it working by changing envvar to _envvar but was able to resolve by changing the apache port from 8888 to 80 then noticed I was missing the mod_example.so. See how I resolved below:
Why won't Apache Server start in MAMP?