In Big Sur 11.2, I’m on Local 5.9.9, just re-installed yesterday. Every time I reboot and start a site, I get a port conflict message as well. I see the 502 Gateway error.
I open terminal and run the suggested command. Kill the process running as root for nginx, using the suggested command on the help page you mentioned. There are several other running on port 80, but with my user account.
After that, the site will run after I restart it in Local. Pretty annoying to kill that task every time. I couldn’t find any clues as to why that task is running and how to start it at startup.
MAMP was installed, but I used AppCleaner to remove it. Is it the Local.app running on port 80 or some other MacOS process.
In my case, the port conflict occurs always after a fresh reboot, when starting the first site of the day. Once the master process is killed, it seems to work normally until I reboot.
Hey everyone, thanks for your patience with this! There was a regression related to this port conflict in the 5.10.0 version of Local.
We released 5.10.1 as a quickfix version – can you install that and let us know if you are still experiencing the issues with Local conflicting with itself on port 80?
The specific issue that the 5.10.1 fix addresses was Local not cleanly killing the Router process. This is the process that listens on Ports 80/443 and which directs a request to the individual WordPress site.
Are you still seeing a port-conflict issue on your machine @scottbuscemi?
I’m on 5.10.1+5267 and I’m still seeing a port conflict alert. Everything seems to be running fine, though, aside from the alert and suggestion to use localhost.
Same. Just happened to me when I moved from php 7.4 -> php 8.0 for a site.
Curious if this is also what’s causing my sites to run slow even when xDebug isn’t actively running. I’d expect page speeds to be slow when xDebug is active, but it will still take 8-10 seconds/page even when xDebug isn’t running now.
Same happens here. Local on iMac with Inter processer + Big Sur works well but on my M1+Big Sur combo threre is a port conflict here and there, which means that Local is basically unusable.