Author Topic: can't bind to socket: 0.0.0.0:80 Address already in use (Read 7464 times)

walden · « **on:** September 10, 2020, 04:42:45 pm »

Did a fresh install of Opnsense las night and having no luck starting the web gui.

the command /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf results in : can't bind to socket: 0.0.0.0:80 Address already in use

I've tried manually correcting the file so that the server attempts to bind to 10.0.0.1 with no success.

What am I missing?

walden · « **Reply #1 on:** September 10, 2020, 05:17:37 pm »

managed to wrestle VI to the ground and insert the proper IP address for ip4 10.0.0.1

now when running/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf I get the error:

(network.c.311) can't bind to socket: [::]:80 Address already in use

I am not running ip6. Tried commenting out the server socket line in the .conf file but that causes parsing to fail.

walden · « **Reply #2 on:** September 10, 2020, 05:20:26 pm »

And restarting web services overwrites my changes to the conf file and we are back to an attempt to bind on 0.0.0.0

Fright · « **Reply #3 on:** September 10, 2020, 05:55:06 pm »

this means that some daemon is already listening on the port. why not change the port for the GUI?
then you can see who is listening on :80 in interfaces-diagnostics-netstat-sockets

Quote

And restarting web services overwrites my changes

.conf overwritten from system configuration

walden · « **Reply #4 on:** September 10, 2020, 06:55:04 pm »

Thanks for that. Since it was a fresh install I went ahead and reverted to factory defaults. this cleared the error and I am able to see the GUI. Now for something weird and unexpected.

The GUI will not load from any browser on my Mac (Chrome, Edge, Safari). It WILL load from Microsoft Edge on an Ipad, but not Safari. I occasionally see a CSRF error on Edge, but I have no restrictions on cookies, and even specifically whitelisted the IP.

I am losing my hair!

Fright · « **Reply #5 on:** September 10, 2020, 07:08:54 pm »

yeah. it's really weird.
you shure there is no network conflicts or some?
try to look in dev console in browsers

walden · « **Reply #6 on:** September 11, 2020, 04:58:42 pm »

The weirdness continues. I turned up logging in the Web GUI log and the webserver is seeing the connection. All looks ok. NOTHING in the dev console except an old cookie. Deleted it, and no luck. Going to try to find an answer so if any great ideas (or bad ones!), let me know. Happy to upload logs.

Thomas

walden · « **Reply #7 on:** September 11, 2020, 05:33:51 pm »

I downloaded Opera and all is well. Basically deep cleaned the other browsers - cache cookies and all - all is well. Thanks for your help.

Fright · « **Reply #8 on:** September 11, 2020, 05:39:45 pm »

Congratulations!
maybe you used this ip earlier to access another resource/firewall
deep cleanup is always good

Author Topic: can't bind to socket: 0.0.0.0:80 Address already in use (Read 7464 times)

walden

can't bind to socket: 0.0.0.0:80 Address already in use

walden

Re: can't bind to socket: 0.0.0.0:80 Address already in use

walden

Re: can't bind to socket: 0.0.0.0:80 Address already in use

Fright

Re: can't bind to socket: 0.0.0.0:80 Address already in use

walden

Re: can't bind to socket: 0.0.0.0:80 Address already in use

Fright

Re: can't bind to socket: 0.0.0.0:80 Address already in use

walden

Re: can't bind to socket: 0.0.0.0:80 Address already in use

walden

Re: can't bind to socket: 0.0.0.0:80 Address already in use

Fright

Re: can't bind to socket: 0.0.0.0:80 Address already in use