Webinterface startup issues?

[Sundial]

I just installed a fresh copy of 16.7.r1.  Every time I restart, the web interface takes several minutes to become accessible (after the reboot is complete and I can log into the shell).  The log has several of these after each reboot: "lighttpd[46964]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init".

[franco]

Error message is not related. The web interface starts late, after your network is up, it may be a network setup step stalling during boot. Only way to find out is to look at the boot sequence and see where it "hangs" for a longer time.

[Sundial]

OK.  I'll try to flesh this out a little more.  I thought the SSL error might have been a key since they appear around the log message where I log into the web interface.  Also, maybe a little more info would be helpful....I think the web interface is actually started because when I attempt to login, the browser just spins and spins for a few minutes.  If the web interface weren't started at all, I'd get a quick "reject" error (I would imagine).

[franco]

The error is only in OpenSSL, LibreSSL managed to fix this.

And right, that seems odd if the login was there previously. It couldn't even hang in SSL (cert generation or general handshake), because the page already loaded. It happens that the system can sparsely hang for a few seconds... maybe it's automatically reconfiguring in the background making the port unavailable for a short time.

[Julien]

Curiosity ,
what services are running on your Firewall ? and how many CPU, Memory does it have ?

[Sundial]

DHCP, NTP, Suricata, and Unbound.  Intel Core i3 (quad core) with 4 GB RAM and SSD.  It really is overkill for my situation.