Port conflict, gone through the docs and can’t work out how to fix this issue.
Processes listening to port 80
paddywinc@Paddys-MacBook-Pro-2 ~ % 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 13025 paddywinc 11u IPv4 0x22ac1e74c3aeb5df 0t0 TCP *:http (LISTEN)
nginx 13025 paddywinc 12u IPv6 0x22ac1e74b62ae8b7 0t0 TCP *:http (LISTEN)
nginx 74091 paddywinc 11u IPv4 0x22ac1e74c3aeb5df 0t0 TCP *:http (LISTEN)
nginx 74091 paddywinc 12u IPv6 0x22ac1e74b62ae8b7 0t0 TCP *:http (LISTEN)
PID TTY TIME CMD
13025 ?? 0:00.03 nginx: master process /Applications/Local.app/Contents/Resources/extraResources/lightning-services/nginx-1.16.0+5/bin/darwin/sbi
PID TTY TIME CMD
74091 ?? 0:00.01 nginx: worker process
All sites in Local
Adding or starting WP build in Local
Which version of Local is being used?
What Operating System (OS) and OS version is being used?
MacOS Big Sur
Attach the Local Log. See this Community Forum post for instructions on how to do so:
I’ve noticed a couple other users on Big Sur are having this issue, and it seems like maybe Local isn’t cleaning up the Nginx processes:
Can you try killing those processes and then starting Local?
Using the output from above, you should be able to use those
PIDs like so:
kill 13025 74091
If the computer has been restarted, those processes might be different. Can you give that a try and let me know how it goes?
I’ve been having the same problem recently, but on Catalina with Local v. 5.10.1+5267
Your recommendation re using
kill is a great temporary solution, but I wanted to report that at least in my case, the problem still occurs sometimes.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.