Local by Flywheel v.5.0.6 Error: Heads-up! Local's router is having trouble starting

Support
1

I receive this error on the new v.5.0.6 local:
Heads-up! Local’s router is having trouble starting. View the router log file for more details.
And when I go to log error file the error is:
[emerg] 24560#188: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
Any idea?
Thanks

3 Likes
2

Hello Vasko,
I’m having the same error message, but I can’t find the error log file.
Can you tell me where to find it?

3

Click the menu button at the top left and click Reveal Local’s Log. (On a Mac, it’s under Help.)

1 Like
4

Having the same issue here, and when I try to change the port on the .conf Local changes it back to :80

2019/10/19 17:30:04 [emerg] 21524#6412: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)

Windows 10 Pro, Build 18362

RESOLVED solution provided here https://superuser.com/questions/352017/pid4-using-port-80

  • Launch RegEdit.
  • Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
  • Change the value of “start” to 4, which means disabled.
  • Reboot your computer.
1 Like
5

Thanks myfriendmoses, I have exactly the same router log error message, but this solution didn’t worked for me.
Still with the Heads-up! Local’s router is having trouble starting. error alert in Local Flywheel

I’ll Still looking…

6

Thanks Greg,
As I mentioned in the post below, I’m receiving the 2019/10/19 17:30:04 [emerg] 21524#6412: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions) router error log

I’m still looking for a solution.

7

This means that something else on your computer is using port 80.

8

somehow it solved… Magic happen sometimes!!!
Thanks

9

Hey All!

Not sure if the issue is resolved for everyone in the thread, but @afragen is correct about Port 80 being utilized, which will cause this error to be thrown.

In this previous thread, one of our tech’s Matt shares some good resources on how to track down if the port is being used, and some others have referenced common programs that use this port: Windows Issue: Local's router is having trouble starting This might be helpful if you’re unsure of where to go to next if you’re running up against this problem. :slightly_smiling_face:

1 Like
10

On on macOS 10.14.5 running Local 5.0.6 and getting the “Local’s router is having trouble starting” error. Did a fresh restart to make sure nothing else was interfering.

Error logs have a bunch of…

2019/10/30 11:27:33 [emerg] 2909#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to 0.0.0.0:80 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to [::]:80 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to 0.0.0.0:80 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to [::]:80 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: bind() to 0.0.0.0:443 failed (48: Address already in use)
2019/10/30 11:27:33 [emerg] 2909#0: still could not bind()

But Activity Monitor > Memory doesn’t show anything at all running on port 80 or 443.

I’ve got Local 3.3 also installed, this was just a test of Local 5. But now neither of them work. When visiting the sites in either, they never resolve and timeout.

11

Try the following command

lsof -nP -i4 | grep LISTEN | grep -E "80|443"

For me using Local 5.0.7 I get the following.

nginx     25557 afragen   12u  IPv4 0x8ad3b7a1f646124d      0t0  TCP *:80 (LISTEN)
nginx     25557 afragen   14u  IPv4 0x8ad3b7a1f61894f5      0t0  TCP *:443 (LISTEN)
nginx     25558 afragen   12u  IPv4 0x8ad3b7a1f646124d      0t0  TCP *:80 (LISTEN)
nginx     25558 afragen   14u  IPv4 0x8ad3b7a1f61894f5      0t0  TCP *:443 (LISTEN)
12

I got this:

MacBook-Pro-2:CPOR chriscoyier$ lsof -nP -i4 | grep LISTEN | grep -E "80|443"
figma_age  1196 chriscoyier    3u  IPv4 0x1a3847c9680f45b      0t0  TCP 127.0.0.1:44950 (LISTEN)
com.docke  1303 chriscoyier   55u  IPv4 0x1a3847c8743cadb      0t0  TCP 127.0.0.1:8080 (LISTEN)

Looks like Docker! I QUIT my “Docker for Mac” app, and it weirdly started working. (yay!)

I even re-started Docker for Mac and it kept working, so that’s also good.

Running that command afterward, I get what you got:

MacBook-Pro-2:CPOR chriscoyier$ lsof -nP -i4 | grep LISTEN | grep -E "80|443"
figma_age  1196 chriscoyier    3u  IPv4 0x1a3847c9680f45b      0t0  TCP 127.0.0.1:44950 (LISTEN)
nginx     19531 chriscoyier   12u  IPv4 0x1a3847cb0115adb      0t0  TCP *:80 (LISTEN)
nginx     19531 chriscoyier   14u  IPv4 0x1a3847c9bdad45b      0t0  TCP *:443 (LISTEN)
nginx     19532 chriscoyier   12u  IPv4 0x1a3847cb0115adb      0t0  TCP *:80 (LISTEN)
nginx     19532 chriscoyier   14u  IPv4 0x1a3847c9bdad45b      0t0  TCP *:443 (LISTEN)
com.docke 19568 chriscoyier   50u  IPv4 0x1a3847c9a8daadb      0t0  TCP 127.0.0.1:8080 (LISTEN)

pretty much anyway

13

I’d call that a win!