Help, I am having the same issue with my install on Windows 10.
Hi @Poppi,
Thanks for giving Lightning a try!
Can you please provide Local’s log file? See How do I retrieve Local's log file? for instructions on how to do so.
Also, are you running any other local development web servers such as XAMPP, MAMP, or DesktopServer? If so, be sure that they’re shut down.
Did have XAMPP installed but wasn’t able to do anything. (now uninstalled.) A friend recommended Local by Flywheel.
Got it! Can you please upload the log file here or copy and paste the contents? It looks like quite a bit was cut off the end in the screenshot.
I did a Ctrl+A and pasted the entire contents into a Word document. It’s 33 pages. I have shots of Pages 32 & 33. Let me know if you need previous pages.
Hey @Poppi, can you try dragging and dropping the log file into a response here? That should attach it so that we can view the whole log.
@Poppi, it definitely looks like something is already using port 80, which Local will need to be have access to. If you’ve already removed XAMPP and aren’t sure what else might be bound to that port, you’ll need to do a bit more digging to see what else might be hiding out there.
Here’s a help doc I found that goes through using netstat to identify the process ID and from there, hopefully, you can pin down what is tying things up:
Okay, after going through the process the PID for the program that is associated with Port 80 is 4 and it was only created last Wednesday, Sept. 11th. I have attached a screen shot. Am I safe to “End Task”?
Without knowing what the service is, I can’t really say if that is “safe” or not.
My hunch is that there is a service running that would be better to “stop” than to end the task there (though that might work perfectly fine as well).
Out of curiousity, what happens when you go to a browser and navigate to http://localhost:80?
There are a few ideas on this page about what might be using port 80 with PID 4 -
I experienced this issue. The solution I finally found at https://praveenpuglia.com/make-wamp-work-on-windows-10-technical-preview/ worked for me.
A different, better method to accomplish the same thing - https://stackoverflow.com/questions/30901434/iis-manager-in-windows-10
1 Like
I stopped World Wide Web Publishing Service and changed the setting from Automatic to Manual. Local is now working. Thanks.
1 Like
Similar issue here trying to run 5.0.6 on Windows 10. The router wont start
2019/10/04 12:59:34 [emerg] 10156#12756: 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)
Ok - it was because iis was running on the laptop (for some reason). Problem resolved
2019/10/06 03:13:57 [emerg] 18400#17480: bind() to 0.0.0.0:443 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2019/10/06 03:13:58 [emerg] 14152#7988: bind() to 0.0.0.0:443 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2019/10/06 03:13:59 [emerg] 17844#10604: bind() to 0.0.0.0:443 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2019/10/06 03:14:00 [emerg] 18216#17732: bind() to 0.0.0.0:443 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
…
This looks similar to the issue I had, where something else locally was using port 443, or port 80. Typically this is another webserver, IIS or Apache, running on the local machine.
Poppi,
Thanks for your advice, it works now.
In Laragon you can change ports… in Local can we change ports?
I’m having the same issue on windows 10 and after looking around I still can’t find anything that works.
The solution found here just didn’t work for me because device manager doesn’t seem to have this option in Windows10.
2019/12/26 06:51:42 [emerg] 29060#27732: 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)
Would appreciate any help on this.