MAMP Pro: Apache couldn't be started because the port was already in use

macos apache mamp mamp-pro
Mystagogue picture Mystagogue · Sep 30, 2014 · Viewed 17k times · Source

When attempting to start my servers, Apache fails to start, and MAMP claims that the port ([::]:8888) is already in use.

I have tried virtually every way I know of determining what process is using that port (as well as many of the solutions previously listed on SO), but I get no results. Neither lsof or netstat list anything about port 8888. There does not appear to be anything using this port at all.

I need to either improve my search and find what(if anything) is really using the port, or somehow convince MAMP that the port is not actually in use. Any suggestions?

EDIT: Changing the port to 8887 allows Apache to start. This doesn't change the fact that nothing is using port 8888 and it should work with that port.

Answer

pinkp picture pinkp · Oct 29, 2014

Try going to activity monitor and searching for Mysqld and Httpd and end any processes for them. Then restart Mamp.

Related questions

MAMP Pro 3.05 on Mavericks updated to Yosemite - Apache does not start

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 my Mavericks install, and now that MAMP Pro install …

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

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 uninstalled PostgreSQL and the apache build and tried to restart MAMP. It …

Read More
Why won't Apache Server start in MAMP?

I'm trying to view php files locally on my mac. I'm running Yosemite. I have MAMP installed on my computer. When I press start the MySQL server starts but Apache doesn't. An error message appears saying 'Error. Apache couldn't be …

Read More