core: WebGUI: can't bind to socket: 127.0.0.1:443: Address already in use
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Describe the bug
After some time running opnsense I’ll get a “503 - service unavailable” error when trying to access the WebGUI. Opnsense itself seems to still do its job, however the WebGUI is gone. Killing lighttpd and restarting services via console solves it (as mentioned here: https://forum.opnsense.org/index.php?topic=32540.0)
I noticed this after the last upgrade.
To Reproduce
Steps to reproduce the behavior:
- Run below mentioned version
- Wait a few days
- Try to access WbGUI
- See error
Expected behavior
Would expect regular WebGUI operation and login window.
Describe alternatives you considered
Relevant log files
As in Forum post mentioned, I found the below part in the logs as well. Could not spot any other error related to webgui.
2023-02-20T07:20:07 Error opnsense /usr/local/etc/rc.restart_webgui: The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2023-02-20 07:20:07: (network.c.537) can't bind to socket: 127.0.0.1:443: Address already in use'
Environment
OPNsense 23.1.1_2-amd64 FreeBSD 13.1-RELEASE-p6 OpenSSL 1.1.1t 7 Feb 2023 AMD GX-412TC SOC
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 86 (50 by maintainers)
Commits related to this issue
- system: switch to SIGINT for lighttpd for #6351 — committed to opnsense/core by fichtner a year ago
- system: fix historic oversight in pid vs. name/pidfile reading related to #6351 If we kill a process and want to wait for it we will have to cache the PID file and check this one until it's gone. — committed to opnsense/core by fichtner a year ago
- system: adjust timeout #6351 — committed to opnsense/core by fichtner a year ago
- system: bring stop/start a little closer together #6351 — committed to opnsense/core by fichtner a year ago
- system: use flock while starting lighttpd #6351 — committed to opnsense/core by fichtner a year ago
- system: address a number of web GUI startup problems #6351 — committed to opnsense/core by fichtner a year ago
- system: defer start of lighttpd on newwanip event #6351 Looks like improvements in 23.1.4 made the problem worse, indicating that the direction this is going is a bit doubtful. Instead, funnel the r... — committed to opnsense/core by fichtner a year ago
- system: do not detach on defer ##6351 Same as filter_configure() now. — committed to opnsense/core by fichtner a year ago
So far the WebGUI seems to work. Errors haven’t showed up. Only having the following in the system log at pppoe reconnect:
23.1.6 was released today.
So far webGUI is still alive and kicking. lighttpd logs are clean with only server stopping/starting messages.
Within system logs I found the following on yesterday’s reconnect:
On today’s reconnect (5am) and firmware check (7am) I get the following:
Does that help?
Thanks a lot! Did a reboot before applying, so any silly state is hopefully cleared up. Applied the patch (I guess reboot won’t be necessary to activate) We probably will see tomorrow or on Monday how it works.