Archive > 19.1 Legacy Series

web service fails to start

(1/1)

osn1803:
Hello all --

It looks like there's a startup order problem in some cases.  I'm finding that lighttpd fails to start at boot, but will happily come up if I issue "reload all services" at the console, and is stable after that.  /var/log/system.log has this to say at boot time:

Mar 10 20:29:15 fw01 opnsense: /usr/local/etc/rc.bootup: The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2019-03-10 20:29:15: (network.c.309) can't bind to socket: [<inet6addr>]:443 Can't assign requested address'

... where <inet6addr> is the LAN internal IPv6 address. 

This is the latest published stable build as of today (19.1.3).  The web service is configured to listen only on LAN.  There are three other ifaces present: WAN, WAN_V6 (HE tunnel), and DMZ.   The NICs in use are a 2-port Intel i350 (for LAN and DMZ) and an Asus onboard gigabit NIC (for WAN). 

Seems that lighttpd is trying to start before all interfaces are fully configured.  Connecting via ssh (or to the console) and issuing "Reload all services" clears it right up.

Let me know if there's other information I could provide that might aid in diagnosis.

Thank you!

franco:
Please don't use strict binding for the web GUI if you're having issues like this. It will not always work, hence the extra warnings in the GUI.

The security benefit is marginal, but people kept asking for it so we added the feature very reluctantly....


Cheers,
Franco

osn1803:
Fair enough.  Reverting to the default wildcard binding does seem to have satisfied it and resolved the issue.

Thank you very much for the info. 

Navigation

[0] Message Index