I just installed Local for the first time on my MacBook Pro using MacOS Sonoma. I created a new site. Now I am getting a “There is a port conflict with this site’s domain” warning. I don’t want to use localhost because I want the live link features to work. When I click on “Open site”, it goes to an “It works!” page. When I click on the “WP Admin” button, it goes to a 404 Not Found page.
I have tried turning off apache via the terminal. I have checked and can see that nothing is running on Port 80.
I have seen this topic reaching back to 2020, but none of the solutions that worked for anyone else have worked for me.
Please help me resolve this issue.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Creating a new site and starting it always leads to this warning.
System Details
Local Version:
Local Version 9.1.0+6719
Operating System (OS) and OS version:
MacOS Sonoma 14.3.1
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
The only other developer application I have installed on my system is MAMP, however, I am not using it. Does simply having MAMP installed on my computer lead to this port conflict with Local?
I wouldn’t think it’s a problem unless it’s running side by side. Even if you’re not actively using it have you used it recently? Could it still be running any processes?
As a test you could try uninstalling it to see if that frees up your Site Domains port.
I just updated to MacOS Sequoia, and I’m still facing the same issue. I ran a full check of what processes are running, and there is no port 80 or 443 in the list. It seems like there must be some way to figure out why Local by Flywheel keeps saying there’s a port conflict. Does local have an error log that would show more information about the source of this error?
and saw that there were a couple processes running.
I entered
sudo apachectl stop
but that didn’t stop the processes for me. It turns out this command stopped the Homebrew apache install, but not the built-in one. To stop the built-in apache install, I used this command:
sudo /usr/local/bin/apachectl stop
and that finally stopped the processes and, lo and behold, the port conflict was gone!
At this point, I still had an issue with being able to access my admin page but not the homepage, which would go to the "It Works!" page, but that may have had something to do with me playing around in the `/etc/resolver/` directory when I was pulling my hair out trying to figure out what was causing the port conflict. It looks like there needs to be a file in the resolver directory titled "local" with the contents being `nameserver 127.0.0.1`
Hope this helps others in the same unusual predicament I was in.