Back to Blog
Mamp not starting mysql server6/27/2023 ![]() When MAMP was closed, the console output was Regarding the first problem (Apache Port in use by another program), I opened up Terminal and > sudo lsof -i -P | grep -i "listen" to see which ports would show up. But, when I tried to log into the site with a dummy user account I received a "SQLSTATE Can't connect to local MySQL server through socket ' /Applications/MAMP/tmp/mysql/mysql.sock' (2)" message. I opened Chrome and entered the url of a site I'm developing locally and it showed up with no problem. I clicked 'Start Servers' again and got a message stating, "Apache couldn't be started because port 8888 is in use by some other software." Weird since I haven't made any changes to the system or application, or installed any updates. ![]() Which sparked the idea.Īfter restarting MAMP, I noticed the MySQL Server checkbox didn't turn green as it usually does. Luckily, i just had read an interesting article explaining how to set up Nginx in front of Apache to serve static and dynamic independently to optimize performance. I simply set Nginx to another random port, hit the "OK" button and no error appeared.Īll my localhost sites are working just as they were before the update. Resulting an an error since both are set to use the same port. When it hit me! When hitting the "Set Web &MySQL ports to 80 & 3306" button in MAMP, MAMP sets port 80 for Apache AND Nginx. Tried a lot of suggestions and fix out there, but none of them worked for me. I ran into the very same problem after upgrading to yosemite and the MAMP Version 3.0.7.3. Go to the MAMP configuration and change the port address 8888 to any other address MAMP->Preferences->Ports->Apache Port
0 Comments
Read More
Leave a Reply. |