WebGUI unaccessible for 3-4 minutes --> when modyfing "Interfaces"

[AES777GCM]

Dear OPNsense team,

I got issues [OPNSense Community Edition 24.7.8] which may look like an old topic for you // seen in https://github.com/opnsense/core/issues/5516

Every time I change anything in one of my INTERFACES (no matter what changes and which INTERFACE) the WEBGUI becomes inaccessible for nearly 3-4 minutes after pushing "APPLY". After drinking 1 more coffee I can log in again a new websession and go on with configuration.

Please have a look over this topic (again?).
If anybody has any kind of solution I'll highly appreciate let knowing me.

Thanks everybody in community and especially the MASTERS of the System - your product is GREAT!!!

cheers,
Udo

Code Select Expand


2024-11-13T18:14:44 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T18:10:37 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T18:10:37 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 5504
2024-11-13T18:10:37 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T18:07:11 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T18:00:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T18:00:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 40240
2024-11-13T18:00:06 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T17:56:56 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T14:27:26 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T14:27:26 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 85278
2024-11-13T14:27:26 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T14:23:58 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T14:19:20 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T14:19:20 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 33189
2024-11-13T14:19:20 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out

[Monviech (Cedrik)]

Are you using a LAGG as interface?

[AES777GCM]

There is no LAGG Interface.

LAN (em0)
WAN (em1)
LAN2 (em2)
WireGuard (wg1)

[Monviech (Cedrik)]

Hmm okay no lagg or vlan means probably no switch issues. Just wanted to check. I sadly cannot help with lighttpd issues. Did you try reverting the webgui to HTTP and see if you have the same issue over HTTP? Just for reference.

[AES777GCM]

It doesn't matter if I'm using http only or https with acme certificate.

I just re-installed my system "fresh".
And after uploading my config file OPNsense is working fine - including the "not accesible WebGUI Problem" which came back too.

[AES777GCM]

Hello Franco and team,

the following phenomenon:
OPNSENSE 24.7 freshly installed --> run an "update from console" to 24.7.8 via root login --> rebooted --> login to WebGUI from LAN --> run initial settings === Everything fine so far.

Then I go to INTERFACE / WAN and just click on "Prevent Interface Removal" --> save (good so far) and then on "APPLY"

Now the problem starts - the WEBGUI makes a "graceful shutdown" - but then does not start as expected directly afterwards.

Code Select Expand

2024-11-16T13:19:24 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-16T13:19:24 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 86795
2024-11-16T13:19:24 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-16T13:15:22 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-16T13:14:50 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-16T12:14:50 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 55307
2024-11-16T12:14:49 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-16T12:12:19 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)

While the struggling 3-4 minutes between automatic restart i tried via shell to "restart all services" - when showing "Web GUI" it shows status "locked".

This behaviour I got on 2 pieces of hardware which have served me well for years.
- HUNSN FW6A (Intel 3865 + 6 x Intel NIC 211)
- Fujitsu Futro 720 (AMD GX 222 + INTEL NIC)

The click on "prevent interface removal" is more or less an example - I could click anything on any Interface - after "APPLY" the WEBGUI struggles like shown above.

Should I be the only person on this planet which this problem? I don't think so.
Please give any kind of solution a try.

[Patrick M. Hausen]

Did you change the interface for the web UI to anything but "All (recommended)"?

[AES777GCM]

No - its exactly as i said.

Fresh install - update to 24.7.8 - initial setup - and on first interaction in wan / lan interface it is struggling as mentioned before.

I didn't change anything in "administration" panel.

[Manfred.Knick]

Confirmation: Similar under [ BE 24.10_7-amd64 ] .

Example:

-> Interface -> select LAN interface -> enable IPv6 :
. . . "IPv6 Configuration Type" = "Track Interface"
. . . "Assign prefix ID" = 0x11

-> Save -> Apply

-> WEB GUI unresponsible for 3'..4'
-> WEB GUI becomes responsible by itself afterwards; no need to reboot et al.

[Manfred.Knick]

Strange:
During this time, access to other websites works as expected - not being blocked

[AES777GCM]

In the 3-4 min period of WebGui being unaccessible everything beside works as it should.

But this behaviour is very annoying.
If developers wants, I can send my Fujitsu in for further testings.

[AES777GCM]

I rolled back to a new installation of 24.1.10_8 and everything is working fine - even the WebGui.
Until further notice I avoid the 24.7 series.

@Team: Please have a look on my posted (and from 3rd site confirmed) issue.

[Monviech (Cedrik)]

Can you try your exact same configuration in a VM and replicate it there?

I have like 10 OPNsense VMs and 4 real hardwares I use for testing stuff and I don't have this issue. It must mean for you it's either something related to your hardware, or a general configuration issue which you do with each OPNsense you deploy.

If you can replicate it in a VM with a minimal configuration, e.g. in proxmox, hyper-v, kvm, esxi..., please provide the config.xml file (of course be careful with passwords etc...)

[AES777GCM]

There is no need for special config file - as I said two times before - FULLY FRESH INSTALLATION - and on first switch action in WAN it struggles (on my well-trusted piece of hardware)

But - I tried in a VM (Virtualbox) and 24.7.8 - even GUI - is working fine there.

But that's not my intention - it should run on industry standard "bare metal" as previous versions - and there is something broken in 24.7x. As one former guy confirmed - even in actual Business Edition [BE 24.10_7-amd64] when using bare metal installation.

24.1.x is working great on my bare metal hardware.

[Monviech (Cedrik)]

Can the scope of that issue be reduced to IPv6 configuration on these interfaces?

Does the issue happen if IPv6 Configuration Type is set to "None"?