Starting web GUI...failed.

Started by Newbiewifi, July 11, 2018, 07:07:15 PM

Previous topic - Next topic
There is warning dialog when you select explicit interfaces under System: Settings: Administration. It's best to uncheck (really leave unchecked) the selection and let the web GUI bind to all addresses.

I'll work on this post-18.7, but we need to get 18.7 out the door so priorities stay there.


Cheers,
Franco

I ran into the very same situation: After updating the official recent installation image (18.7, amd, vga from the OPNsense website) to 18.7.9, after a reboot the web GUI failed to start! The problem seems symptomatic for this update, it happened on two test sites were we try OPNsense. Most frustrating, one site is remote and ssh is disabled.

As the thread indicates, the last question was how to revert the binding to a specific address/interface? I guess the last response is a kind of ironic, since no web GUI, no chance to change. Funny.

Is there a way to configure/uncheck this manually?

Regards
Ex nihilo nihil fit!

Quote from: Drohne on January 04, 2019, 12:22:43 PM
Is there a way to configure/uncheck this manually?

Using vim to edit the configuration (via SSH) and reload everything you should be able to change almost everything running on OPNsense.

I can offer you a workaround - replace lighttpd by nginx:

1. Install the nginx plugin
2. change this line in the configuration template (uncomment the import line): https://github.com/opnsense/plugins/blob/master/www/nginx/src/opnsense/service/templates/OPNsense/Nginx/http.conf#L42
3. generate the server config "configctl template reload OPNsense/Nginx"
4. start the service "configctl nginx start"

Then the web interface is served by nginx (please note that this is currently not officially supported by core or the plugin itself, so it may cause some trouble with the next update*). Please keep in mind that even if it is faster, you should not stay with experimental code because the core currently cannot restart the web interface etc. when nginx is serving it and it tries to start lighttpd and will obviously fail (port is in use).

The main reason why the plugin ships this code is that my original intention was to share the port between the web interface and the reverse proxy so both can use the standard ports (80, 443).

* nginx plugin update => change in (2) will be lost; core update => nginx is started after lighttpd and cannot start because the port is in use (which can be prevented by also overriding the listen directive (https://github.com/opnsense/plugins/blob/master/www/nginx/src/opnsense/service/templates/OPNsense/Nginx/webgui.conf#L11-L12)



# vi /conf/config.xml

Find <system>
Find <webgui>
Find <interfaces>

Delete <interfaces>a,b,c,d</interfaces> line

Save the file.

# /usr/local/etc/rc.restart_webgui


Cheers,
Franco