Local Community

"Heads-up! Local's router is having trouble starting" on windows 10

This is my first site at Local. When I created a site I got this message
My computer is running on windows 10 64bit.

The log file of of local’s router
2019/12/28 23:37:29 [emerg] 16340#6528: 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)
2019/12/28 23:37:30 [emerg] 22860#23500: 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)
2019/12/28 23:37:31 [emerg] 23244#23356: 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)
2019/12/28 23:37:32 [emerg] 23628#23632: 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)
2019/12/28 23:40:03 [emerg] 22316#1484: 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)
2019/12/28 23:40:04 [emerg] 23700#24020: 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)
2019/12/28 23:40:05 [emerg] 8320#23348: 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)
2019/12/28 23:40:06 [emerg] 24268#23312: 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)
2019/12/28 23:40:12 [emerg] 15160#22696: 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)
2019/12/28 23:40:13 [emerg] 24304#20692: 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)
2019/12/28 23:40:14 [emerg] 23700#22676: 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)
2019/12/28 23:40:15 [emerg] 24100#9560: 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)
2019/12/28 23:40:29 [emerg] 22792#7244: 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)
2019/12/28 23:40:32 [emerg] 22848#22972: 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)
2019/12/28 23:40:34 [emerg] 25196#25200: 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)
2019/12/28 23:40:35 [emerg] 25232#20144: 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)
2019/12/28 23:40:36 [emerg] 24336#8888: 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)
2019/12/28 23:40:37 [emerg] 24100#24788: 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)
2019/12/28 23:45:06 [emerg] 16536#24844: 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)
2019/12/28 23:45:07 [emerg] 22724#22748: 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)
2019/12/28 23:45:08 [emerg] 20748#23688: 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)
2019/12/28 23:45:09 [emerg] 24376#23184: 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)
2019/12/28 23:51:25 [emerg] 23980#24156: 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)
2019/12/28 23:51:26 [emerg] 11508#24300: 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)
2019/12/28 23:51:28 [emerg] 24680#13492: 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)
2019/12/28 23:51:29 [emerg] 13784#23720: 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)
2019/12/28 23:57:08 [emerg] 19244#23260: 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)
2019/12/29 00:12:33 [emerg] 22572#16352: 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)
2019/12/29 00:12:34 [emerg] 25428#9480: 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)
2019/12/29 00:12:35 [emerg] 4704#23344: 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)
2019/12/30 22:17:19 [emerg] 21192#17056: 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)
2019/12/30 22:17:20 [emerg] 22452#13404: 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)
2019/12/30 22:17:22 [emerg] 7328#14360: 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)
2019/12/30 22:17:23 [emerg] 22160#7720: 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)

There is some other process running on port 80 on your computer. You must exit that process.

Same issue.Win 10. I have IIS running on port 80. Can Local run on a different port and how?

Hey @elveez

For these kinds of situations where there’s already another app that’s taking either port 80 or 443 (the defaults for HTTP and HTTPS) Local has a different “Router Mode” that can be accessed from “Preferences > Advanced”

The “Localhost” option will change the domain so that it uses a different port like localhost:10021

Thanks Ben! That solved it.

1 Like

Also, this would be useful to place on Flywheel site help section, an easy fix once you know how to do it.

@ben.turner Worked for me too. Thanks SO much, man!

1 Like

So I know localhost mode is an option, but isn’t router really just nginx and couldn’t that be configure to listen to 8080 instead of 80? Has anyone tried that?

I have provided solution for this issue here: https://wp-ask.com/question/heads-up-locals-router-is-having-trouble-starting-error-on-local/

I hope this helps.

You might be able to hack that into something that works, but I think that would be pretty fragile and ultimately would start breaking down in hard to troubleshoot ways. The main things that come to mind are that Local does a number of things to update URL and since it’s not considering the fact that the router would be listening on a different port than the default 80 – the actual URLs in the WP site’s DB wouldn’t be correctly updated.