[SOLVED] Lost access to web interface after upgrade to 16.7

Started by marius, July 29, 2016, 05:03:39 AM

Previous topic - Next topic
After upgrading to 16.7 I can no longer access the web interface.  I can access via SSH and I can confirm the machine is upgraded to 16.7. I tried opnsense-bootstrap which ran fine, rebooted and still no web interface. I can confirm with nmap that port 443 is open. What logs should I be looking into?

have the same issue, webconfigurator rules got removed and lost access

Hi there,

Can you check whether the service is running?

# pgrep lighttpd

The logs can be skimmed with

# clog /var/log/system.log

And you may be able to catch an error with restarting manually:

# /usr/local/etc/rc.restart_webgui

And checking for PHP errors under:

# cat /tmp/PHP_errors.log


Cheers,
Franco

The service just wasn't running.

#pgrep lighttpd
returned nothing

# /usr/local/etc/rc.restart_webgui
Restarting webConfigurator...done.

# pgrep lighttpd
66099

I'd like to add that I yesterday had tried "11) Restart web interface" from the console with no effect.

In the logs I found the following messages during the upgrade:
# grep lighttpd /var/log/system.log
Jul 28 18:24:52 roadblock lighttpd[85939]: (mod_fastcgi.c.2390) unexpected end-of-file (perhaps the fastcgi process died): pid: 88888 socket: unix:/tmp/php-fastcgi.socket-1
Jul 28 18:24:52 roadblock lighttpd[85939]: (mod_fastcgi.c.3171) response not received, request sent: 1116 on socket: unix:/tmp/php-fastcgi.socket-1 for /api/api.php?_url=/core/firmware/upgradestatus&, closing connection
Jul 28 18:24:52 roadblock lighttpd[85939]: (server.c.1572) server stopped by UID = 0 PID = 82630
Jul 28 18:24:53 roadblock lighttpd[89899]: (log.c.194) server started

Thanks.

Ok, glad to hear that. What hardware and RAM config do you have for reference?

I'm also seeing this type of messages in the logs, not sure if they're related:

lighttpd[66099]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init

That's a harmless defect of the OpenSSL API, e.g. under LibreSSL this doesn't happen.

Thanks for your installation parameters. At least this wasn't caused by slow hardware or low resources, so no good explanation whatsoever. :(