Local Community

Creating new sites no longer works

Support
#1

Hi, My LBF has stopped working for logging in to new sites. I just get a spinning wheel. So I uninstalled everything and tried to start again. It was a nightmare (understatement) to get it all going. The default install would not install VB so it took a few attempts to get that going and for flywheel to install.
Now when I create a new site I get the orange message bar stating: Warning! Missing hosts entry. The site may be inaccessible. When I click the FIX IT button, I get the Error message: Windows cannot find C:Users\name\AppData\Local\Programs\local-by-flywheel\resources\extraResources\node\node-x674.exe. Make sure you typed the name correctly, and then try again.

The file does exist in that directory.

HELP!

#2

Hey @nothanks –

I’m sorry for the trouble you’ve been having. Much of what you are describing sounds like some sort of security setting, or Antivirus preventing Local from working with the components that it needs to manage sites.

Have there been any recent upgrades to Windows, or any recent changes to security settings?

In addition to answering the above question, can you please provide your local-by-flywheel.log file? See this Community Forum post for instructions on how to do so:

#3

Hi Ben,
Sorry I tried uninstalling, reinstalling again, to the point where something went wrong with the PC and I had to do a system restore.
I was not aware that my Antivirus Software (ESET) would just magically decide to prevent your software from working, nor would I expect Windows updates to prevent your software from working either (surely you test these scenarios)?
So I heard you had released a new BETA version of the sofware, and today, I downloaded, ran and created a new site only to get the following error:

2019/10/05 15:41:10 [emerg] 176#3540: 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/10/05 15:41:11 [emerg] 4052#3536: 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/10/05 15:41:12 [emerg] 4584#8140: 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/10/05 15:41:12 [emerg] 7184#3952: 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/10/05 15:41:57 [emerg] 6212#7404: 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/10/05 15:41:57 [emerg] 5076#3540: 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/10/05 15:41:58 [emerg] 1252#2568: 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/10/05 15:41:58 [emerg] 4352#1392: 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/10/05 15:49:46 [emerg] 7952#7848: 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/10/05 15:49:46 [emerg] 4292#2892: 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/10/05 15:49:47 [emerg] 1516#1768: 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/10/05 15:49:47 [emerg] 5240#4164: 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/10/05 15:51:44 [emerg] 5476#2136: 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/10/05 15:51:44 [emerg] 7484#7140: 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/10/05 15:51:45 [emerg] 6440#5220: 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/10/05 15:51:45 [emerg] 6288#8092: 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)

I understand WordPress, but I’m afraid this means very little to me except I do know my computer is plugged into a socket and is switched on :wink:

#4

You’d be surprised at how fragile a Windows update actually is. We do test for a number of things, but there’s practically an infinite number of variables, settings and apps that can be present and which can be causing problems!

:joy:

As to the details of those error messages: That kind of error is basically saying that Local can’t “bind” to port 80 (the part that is 0.0.0.0:80)

You can think of port 80 as the default place that your computer listens for HTTP requests. Because Local can’t “bind” to that port, it can’t be in charge of responding to requests that the browser makes for the Local site’s domain – ie, when you type in example.local into the web browser.

This can also be due to antivirus software, but it could also be due to another piece of software that is currently using port 80.

Do you have any other tools used for Local development, for example, Mamp? If so, you might try temporarily turning those off, and restarting Local so that it can use that port.

#5