This makes me want to cry! WebGUI instability on all different hardware!

[roohoo]

I have been trying to set up an OPNSense router for quite some time now but each time I get a setup that seems to die some time after between 40minutes and 18 hours.

I have tried two different computers with three different NICs (all with different chipsets at speeds of 10G, 2.5G & 1G), different amounts of RAM, made up of different DIMMS, different storage media (m.2 nvme & sata ssd).  I have tried with versions 25 & 26 of OPNSense.

Initially my network (no vlans or sub domains) was 192.168.0.0/16 but I have reconfigured it to 192.168.2.0/24 in case that was the problem.

I configure OPNSense with a single WAN ethernet connection to my fibre modem (with IP address provided by DHCP) and a single LAN connection to my network (with IP address 192.168.2.1).  I make no further configuration changes whilst trying to get everything to work.

Each time, after an amount of time (between 40 minutes & 18 hours), the webGUI starts to break: Every "display section" of the dashboard will show "Failed to load widget" and the uptime will show something like 20000 days.  Internet connectivity and DHCP services on my LAN do not seem to be affected.  I can still SSH into the server and the system time remains accurate.

I don't know what else to try!  How can I keep getting exactly the same fault on different hardware? Please, learned friends, give me the benefits of your experience and expertise!

[chemlud]

"...and the uptime will show something like 20000 days"

System time fails? Results in all sorts of errors, as time is essential for many, many things on the interwebs. Check NTP. System board time? CMOS battery?

You are really alone with this kind of error...

[roohoo]

Hi

NTP is working fine and the system time is correct.  Even after leaving the machine off for several days, the time remains correct, so the CMOS battery and motherboard time are fine!

I have searched the forum and can't find any similar complaints!  All I know is that I have tried two different computer systems and lots of different components and the outcome is always the same.  Could it be that there might be a device on my network capable of sending packets that are fatal to OPNSense's webGUI?

Thanks for the suggestion.

"...and the uptime will show something like 20000 days"

System time fails? Results in all sorts of errors, as time is essential for many, many things on the interwebs. Check NTP. System board time? CMOS battery?

You are really alone with this kind of error...

[nero355]

I have tried two different computers with three different NICs

Could you post the full hardware specifications ?

Maybe someone recognizes something and can help you out...



To me it sounds like some kind of weird "jump" happening that could be related to bad compatibility with the BIOS/UEFI or some part of some kind of firmware involved, but then I would also expect to see the whole system crash and not just the webGUI to act weird ?!?!

[roohoo]

Interestingly, this afternoon I grabbed another computer: A Ryzen 3900x-powered machine with 128GB of RAM, an M.2 nvme drive, and a Quadro video card. I installed OPNSense with a bare setup (just interfaces configured) and started it up.

Now, around two hours later, I have exactly the same issue: That's a third completely different computer used to install and run OPNSense that has the webGUI die in a few hours of running!

The only connecting factor appears to be my home network!

[Patrick M. Hausen]

Are you running OPNsense for a couple of hours and when you connect to the web UI again, it's not working?

Or are you leaving the UI open for a couple of hours? I vaguely remember the latter not working for some people. I don't know, I never use OPNsense like that. Log in, configure or check stuff, close tab.

[dirtyfreebooter]

yea, have also encountered this, i accidentally had a tab open for a long time, and when i came back nothing was working in the UI, i could ssh, rebooted and the web ui working again. normally i don't do this, but i had the tab up, got distracted, and when i came back things were weird. i looked in the logs, lighthttpd logs, and saw nothing. so i rebooted and moved on with my life, but it was strange.

[OPNenthu]

If it's the timeout issue, then no need to reboot.  OPNsense is fine and it's just the web session that's gone stale.

Hit the browser refresh and log in again.

[dirtyfreebooter]

If it's the timeout issue, then no need to reboot.  OPNsense is fine and it's just the web session that's gone stale.

Hit the browser refresh and log in again.

yea, i think i tried refreshing the page, lol. i even closed the browser and couldn't get to the login screen. all networking seemed fine and like i said, ssh worked and i rebooted it via the console and then the web ui worked again. i didn't report anything because i had nothing in the logs, so nothing was going to done about it (which is fine)

[sopex8260]

The logout logic of opnsense is a bit hit or miss... Most people never realize it because they don't keep sessions open for 4 hours.

This could have happened here.

Also changing from https to http can be catastrophic for up to 1-2 weeks. Chrome in particular if it has connected to a domain or ip using https beforehand, it refuses to acknowledge that http is a real thing.

Generally speaking, I would try incognito sessions.