BUG: Local 5.10 asserts there's a port conflict

Issue Summary

Starting any site shows the Port Conflict error

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    All

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    Not relevant

Replication

Run local 5.1.0. Start any existing site.
After a few seconds, Local will assert that the site has a port conflict error

System Details

  • Which version of Local is being used?
    5.1.0

  • What Operating System (OS) and OS version is being used?
    macOS 11.2.1

More info:
Looking at what else is on the ports, get this:
rick@ricks-MBP ~ % sudo lsof -i:80; sudo lsof -tnP -i:80 | xargs -n 1 ps -p
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nginx 93326 rick 11u IPv4 0x1260b17e07d7d497 0t0 TCP *:http (LISTEN)
nginx 93326 rick 12u IPv6 0x1260b17df90271ff 0t0 TCP *:http (LISTEN)
nginx 93327 rick 11u IPv4 0x1260b17e07d7d497 0t0 TCP *:http (LISTEN)
nginx 93327 rick 12u IPv6 0x1260b17df90271ff 0t0 TCP *:http (LISTEN)
PID TTY TIME CMD
93326 ?? 0:00.02 nginx: master process /Applications/Local.app/Contents/Resources/extraResources/lightning-services/nginx-1.16.0+5/bin/darwin/sbin/nginx -c /Users/rick/Library/Application
PID TTY TIME CMD
93327 ?? 0:00.07 nginx: worker process

NOTE: I get this even after quitting Local. If I manually kill those 2 processes the site will launch fine. It seems Local is not releasing ports when quit.

MORE:

Reverted to 5.9.9 and this works fine.

Sorry about the hassle with this. There was a regression in 5.10.0 related to Local’s router.

That should be fixed in the 5.10.1 version of Local:

See this related topic in the forums: Port conflict with this site’s domain

I responded to another thread with this info so apologies for the duplication, but I’m still seeing a port conflict alert with 5.10.1+5267. Nothing else seems to be affected—it’s just the alert notification.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.