OPNsense Forum

I was looking forward to a new dashboard, after upgrading to 24.7 but it's still a bit disapointing.
As the attached picture shows, some of the widgets do not work (yet).
"System Information" sometimes shows after a page refresh, but after a short while it shows "failed" again.
Are these known issues for all of the failing widgets?

Hope we get a hotfix soon.

Not to disappoint, but I saw something similar while testing 24.7 on an underpowered APU1 where half the dashboard failed to load -- possibly just due to arbitrary timeout limits that the hardware couldn't fulfil according to the JS console.

Would be easy to fix, but also highly localised problem.


Cheers,
Franco

Yes, I have same problem on several platforms in multiple cloud environments.
VM is running on small cheap VPS, but doing doing good job for money.
Tested, that each API request takes 2-8sec to load.
UI has some timeout set to 1 sec, therefore everything failing.

Thanks for confirming. I'm sure we'll find a good solution here until 24.7.1.


Cheers,
Franco

Running into the same issue on a DEC850 which should have enough CPU resources.
There must be something else going on that is not caused by low performance systems.

Since JS is client side it could also be a slower client. It's pretty hard to tell without sitting in front of it.


Cheers,
Franco

I had this kind of problem while testing 24.7 betas... I assumed that it was because the lack of resources on my testing environment.
Celeron 11 or 12 years old... I was running a virtual router and managed it by a virtual desktop.... veeeeery slow, but enough for testing purposes.
Now that I've updated my main router I didn't see this error anymore.

Was having this issue using Firefox, tried Edge and it works no problem. I did not have issues with the betas on Firefox.

I do run into the issue on Edge.

My test system is an i5 6500 with 8gig of Ram. So am not sure if it would be a low resource issue as mentioned before.

Its clear from browser dev console:
On first there is 1sec timeout on UI enforced.
On second there is real load time of response. Response is ok, JSON is ok, return code 200-ok.

Mine were all broken too - clear your browser cache and all will be amazing.
Great upgrade Team!

wait, I've found a problem...

I have an APU2 and my widgets fail to load from time to time too.
Is it possible to just use the old dashboard? Less bling-bling but at least working reliably.

Nope.

it seems pure coincidence which widget loads and which "failed to load widget" (though Disk always loads)
tried Firefox / Chrome, empty browser cache, new browser profile.. no difference
when removing and adding the widgets they work .. until next load of Dashboard
APU.4

Can confirm issues remain after _5, and I'm seeing it on much more powerful systems such as N5105 or J3710 CPUs with 8GB RAM. I checked whether removing/re-adding the widgets makes a difference and it doesn't.

Onwards to 24.7.1, things will improve shortly.

After updating to 24.7_5 its the same. I have some functioning widgets, some not, and the weird part is that i cant delete at least the  Traffic Graph if i press the X to close it.
I cant get any cpu reading, and this a beefy boy: Ryzen 5 3600X

Ps: i am running opnsense inside a VM. I can see traffic inside of Report --> Traffic.

PS2: with debugging enabled what i am mostly getting is Failed to load content for widget: XXXXXXXX, Error: TypeError: selector.replace is not a function

Having the widget problem too, in FF & Chromium (all I tested). Install is virtual in the Oracle Cloud (OCI) but very good performance I would say.

Which widget works and which not seems to randomly change.
(https://forum.opnsense.org/index.php?action=dlattach;topic=41729.0;attach=36404;image)

Also the same. I tried updating 24.7_5 but the issue is still there.

I tested FF, chrome, Edge on Linux, Windows and Safari on iOS. Rebooted the router many times and only one browser logged in.

Clear cache many times.

No solution. I think we have to wait for opnsense team to give us an update that fixes the issue.

Reduce the amount of widgets to most critical.  I reduced to three, Firewall, Traffic Graph and System Info. If I go beyond five, I see fail to load.  Works for me until there's a resolution.

Another issue seems to be the web server having too few concurrent connections set up:

https://github.com/opnsense/core/commit/724f8494d6

# opnsense-patch 724f8494d6
# configctl webgui restart


Cheers,
Franco

The "interface" widget seems to be the issue on my APU2. Disabling it and the rest of my widgets starts to work.

Quote from: bytequest on July 27, 2024, 10:18:18 AM
The "interface" widget seems to be the issue on my APU2. Disabling it and the rest of my widgets starts to work.

No interfaces widget here... Default dashboard, with thermal sensors added (to check the other reports here) Yet (even with 724f8494d6 applied):

EDIT: When I remove the thermal sensors widget (which most of the times does not load anyway, it mostly "unbreaks" the announcements widget as well. This thing needs some serious polishing and realistic timeouts.

Is there any way to revert back to "old" dashboard? In my case, even when using browser never used before to access updated OPNSense it's failing - widgets are not loaded, in some error status and also it can take several seconds when WebGUI is somehow responsible again. Thank you.

Beyond downgrade, nope...

Another widget issue here, unfortunately.
Unable to add widgets due to the drop down menu disappearing immediately after clicking on the desired widget to add, and therefore unable to apply changes.

Change your theme to the OPNsense one until it gets updated

Quote from: franco on July 27, 2024, 10:12:39 AM
Another issue seems to be the web server having too few concurrent connections set up:

https://github.com/opnsense/core/commit/724f8494d6

# opnsense-patch 724f8494d6
# configctl webgui restart


Cheers,
Franco

Things are much better with this patch, not perfect though.

Here's what I'm seeing:

Connected over ZT - slower link - things look fine. No other connections to the dashboard.

Connected both over ZT and locally behind the FW - occasional widget crashes locally, sometimes self-healing, relading the page fixes it. Meanwhile the widgets on the ZT/slow link have crashed and not even after multiple reloads they don't recover.

Seeing these messages the dev tools console in a loop:

The connection to https://192.168.EDI.TED/api/diagnostics/traffic/stream/1 has terminated unexpectedly. Some data may have been transferred. BaseWidget.js:195:27
Uncaught (in promise)
Object { xhr: {...}, textStatus: "error", errorThrown: "" }
4 Traffic.js:197:5
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: swap, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: firewallstates, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: memory, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: swap, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: firewallstates, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: memory, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: services, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: thermalsensors, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfacestatistics, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: interfaces, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: gateways, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17
Failed to load content for widget: systeminformation, Error:
Object { xhr: {...}, textStatus: "timeout", errorThrown: "timeout" }
opnsense_widget_manager.js:486:17


As a workaround I found it useful to delete as many widgets as possible and keep a small number that you really care about until there is a fix.

The picture plugin was very handy as there was no other easier way to view what router you were managing when Dashboard glancing.
Either that or a new plugin that simply has "n" simple text fields that can store custom info.

Quote from: hoondi on July 28, 2024, 11:47:07 AM
The picture plugin was very handy as there was no other easier way to view what router you were managing when Dashboard glancing.
Either that or a new plugin that simply has "n" simple text fields that can store custom info.

Maybe a widget for "os-net-snmp" plugin? These are standardized after all, and can additionally be used via SNMP too.

- sysName
- sysLocation
- sysContact

Wish I could do even that. Thought I could start with zero widgets, but saving the dashboard settings doesn't even work. Also the traffic graph widget cannot be closed. Furthermore the selection menu runs underneath the "Add Widget" page.

Until the other themes get fixed, that can be cured by using the standard opnsense theme...

For me on APU3 the Announcements-Widget is breaking all others. After removing it, the others I need (System Information, Memory, Disk, Thermal Sensors, Gateways, CPU, Interface Statistics) are working fine.

Update: It seems to me that just too many Widgets break all together. I also applied the patch btw.

For me, i also found that there are widgets that i cant edit or delete, for example the traffic graph one.

Folks, there are at least 3 separate issues with the new widgets (apart from cosmetic problems with individual widgets):

1. On some themes, the settings cannot be changed. Solution: use the opnsense theme until they get fixed.
2. The number of connections in the web server is limited, so on slow CPUs or if you open the dashboard multiple times, they will fail. Solution: Use the patch or wait until monday's hotfix.
3. The timeout for any widget to show up is fairly small. That means that on slow CPUs, some widgets may fail. IDK if that will be addressed shortly.

Quote from: meyergru on July 28, 2024, 02:29:37 PM
3. The timeout for any widget to show up is fairly small. That means that on slow CPUs, some widgets may fail. IDK if that will be addressed shortly.

Any idea where's the timeout set? Need to patch it to some sane values and see how it goes; as it is, the dashboard is going to be just unusable on lots of boxes I manage. (#2 does not help there - broken with just default install.)

I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

Quote from: meyergru on July 28, 2024, 04:24:13 PM
I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

Hey, i just changed the value from 1000 to 10000 for a quick test. my widgets are all loading now. (just in case i enabled basically everything.

I had the same issue with many widgets. as long as i only had 3-4 active it worked and it did not depend on which widget it was as long as there were few.

CPU used: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz (2 cores, 2 threads)

Quote from: meyergru on July 28, 2024, 04:24:13 PM
I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

Cool, that definitely helped.  8)

If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

Quote from: meyergru on July 28, 2024, 06:22:07 PM
If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

There seems to be already one covering the not loading widgets: https://github.com/opnsense/core/issues/7651

Quote from: doktornotor on July 28, 2024, 06:28:02 PM

Quote from: meyergru on July 28, 2024, 06:22:07 PM
If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

There seems to be already one covering the not loading widgets: https://github.com/opnsense/core/issues/7651

Yes, but the patch contained in that issue only covers #2 from my list above.

My 2c here.
No widget load even after:
/* Connection timeout params */
        this.timeoutPeriod = 10000;
        this.retryLimit = 3;

Have a test fw running just upgraded it from 24.1.10_8
Using standard theme.
It's a vm in hyper-v with plenty of resources.

Let me know if I can contribute with anything.

Quote from: iorx on July 28, 2024, 06:49:27 PM
My 2c here.
No widget load even after:
/* Connection timeout params */
        this.timeoutPeriod = 10000;
        this.retryLimit = 3;

Did you apply the lighttpd configuration patch as well and restarted the GUI? Patching the timeout alone will probably make things even worse.


https://github.com/opnsense/core/issues/7651#issuecomment-2252096655

Of course I didn't :o because I didn't read everything. Sorry for that noise :-[

Now, I've applied it. But still all widgets are broken.
Did a Dashboard Restore Default. No widgets.
And a reboot. No widgets.

root@fw:~ # opnsense-patch 724f8494d
Fetched 724f8494d via https://github.com/opnsense/core
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|From 724f8494d64074e0384b9f593e699daf2d84d604 Mon Sep 17 00:00:00 2001
|From: Ad Schellevis <ad@opnsense.org>
|Date: Fri, 26 Jul 2024 08:49:38 +0200
|Subject: [PATCH] webgui: long lasting calls and locking the request pipeline.
| work-around for https://github.com/opnsense/core/issues/7651
|
|The number of php processes we offer to lighttpd is quite low (2 x 3), which results in a global lock when 2 dashboards are open at the same time.
|Although we should increase the limit, we also should figure out a way to limit the number of long running processes as well.
|---
| src/etc/inc/plugins.inc.d/webgui.inc | 2 +-
| 1 file changed, 1 insertion(+), 1 deletion(-)
|
|diff --git a/src/etc/inc/plugins.inc.d/webgui.inc b/src/etc/inc/plugins.inc.d/webgui.inc
|index 88cf886d100..6aaef8cd882 100644
|--- a/src/etc/inc/plugins.inc.d/webgui.inc
|+++ b/src/etc/inc/plugins.inc.d/webgui.inc
--------------------------
Patching file etc/inc/plugins.inc.d/webgui.inc using Plan A...
Hunk #1 succeeded at 239.
done
All patches have been applied successfully.  Have a nice day.
root@fw:~ # configctl webgui restart
OK
root@fw:~ # reboot


No idea. Look at the developer console output (F12 in Chrome-based browsers, no idea about FF).

And... it's working!

Went away for a while and came back check on replies. Reloaded the page (ctrl+r) with the dev console open and they showed up.
Strange: Tried the reload page thingy right after the reboot too with "no go" on the widgets.
So, I got no clue what's going on here, some timeout/cache maybe.

(F12 in FF too.) Checked the console output, and before reload there was a bunch of errors, didn't grab that sadly.

Also juggled around with them and saved the layout. It stuck, so guess everything is dandy now! :)

Thank you for the extremely fast response and assistance here, KUDOS!

Latest update 24.7_9 seems to have resolved all my known GUI and timeout issues.
Thanks guys.

Hi @Franco.

Just updated to 24.7_9 and the problem for me at least is getting worst. Now i lost also some widgets regarding vpn (openvpn and ipsec).
Also, the widget that will not die (traffic report), still refuses to close with the following error:

Uncaught TypeError: this.charts.trafficIn is null
    onWidgetClose https://pfsense01.net.xpto/ui/js/widgets/Traffic.js?t=1722259354715:243
    _onWidgetClose https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:693
    _onMarkupRendered https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:412
    jQuery 2

Thanks for your help!

@xupetas

In your case I would try to remove the traffic widget and reload the page.


Cheers,
Franco

@Franco

That error i pasted... is what i get when i try to remove the widget. It will not allow me to remove it. I press the X on the top right corner of the widget and it throws that error i pasted and it will not delete the widget.

Uncaught TypeError: this.charts.trafficIn is null
    onWidgetClose https://pfsense01.net.xpto/ui/js/widgets/Traffic.js?t=1722259354715:243
    _onWidgetClose https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:693
    _onMarkupRendered https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:412
    jQuery 2

Is there a configuration file that i can delete/truncate on the server so all the widgets are reset and i have an empty and clear homepage and go from there?

Thanks for your help.
Cheers.

Hi @Franco. Do you have any idea on how i can reset the entire widget configuration so i dont have any widgets loaded?
See what happens on my previous reply to this thread when i try to delete the ones that are hanged.

@xupetas

Can you try this patch? https://github.com/opnsense/core/commit/4501c593ecd

# opnsense-patch 4501c593ecd


Cheers,
Franco

@Franco

Thanks. I can delete the widget now. Thanks so much.
I added again the ones that would not work, and some are still dead, for example the CPU and OpenVPN connections.

But at least i can have a clean screen. 

Thanks for your help! I will wait for the others when the team has time to address them.

Kindly,
Nuno

@Franco

Hi Franco,
the patch work for me also. After the patch saving widgets also work... before I tried to add Thermal Sensor Widget withou sucess. After the patch it works.

The Traffic Widget also didn't display any kind of information. It's complete empty (white)

BR Andreas, thanks for the patch :)

Thanks for confirming. There are more patches in the pipeline. We will get there step by step.


Cheers,
Franco

My LANNER PFW600 (at OPNsense 24.7_9) starts the Lobby: Dashboard OK, but eventually stops working on my Linux laptop dedicated to being a OPNsense management laptop connected to a local network access only port on the LANNER (Browser is the current Linux Firefox ESR variant running on a System 76 EduBook Starling 2; EduBook's OS is Debian 12.5 with updates).  A 2nd browser just activated for 24.7 dashboard testing is an Iridium (Chrome fork) running on a Windows 10 system on a Toshiba Portege laptop.

The Linux machine, even when the only program that is active is the browser running the OPNsense dashboard and a Firewall: Log Files: Live View eventually ends up with the OPNsense dashboard no longer working when the dashboard no longer has focus and always if the screen saver kicks in.  The Firefox ESR complains about the drag on browser performance due to the dashboard javascript.  The CPU widget appears to stop working first, then every other widget quickly comes to a halt.

There may be a problem with the widgets re-initializing after being suspended by the OS due to not having focus (swapping and laptop/browser memory constraints are not a factor).     The dashboard responsiveness slowly degrades even if focus is kept on the dashboard web page -- there may be a problem with flags not being cleared, memory leakage, memory not being freed.

Testing of the Windows 10/dashboard is ongoing, will update this post with a reply if insights occur . . . . . (the Windows 10/Iridium machine's dashboard display is still working after 30 minutes . . . . .).

Having an option to run the old dashboard on my Linux laptop would be a workaround.

The Windows 10/Iridium's OPNsense dashboard is still working fine after two hours have passed -- even after a forced screen saver (i.e., a Lock).   This is on an old Windows 10 laptop (16 GB RAM) that is missing more than a few OS updates; the Iridium browser is the latest version.  Other activity in addition to the Iridium browser are not affecting the dashboard's widget displays (when focus returns to Iridium's dashboard page, the widgets restart correctly and as expected).

The Linux/Firefox ESR laptop's OPNsense dashboard stops working sometimes only after a few seconds even though there is no other keyboard/mouse activity after an OS restart and only the Firefox ESR is started up.   Whether or not the public Internet access is enabled or not does not appear to affect OPNsense dashboard widgets behavior.

Doesn't matter what browser the Firewall widget and traffic in & out widget not working correctly after grading to 24.7

The upgrade from 24.7.1 to 24.7.2:
* A Linux Debian 12.5 laptop (dedicated to being a firewall management device) with Firefox ESR is unable to run:
  - /ui/diagnostics/firewall/log#Lobby
  - /?url=ui/core/dashboard
  An error message is eventually displayed:  The Connection has timed out
  Linux is no longer usable as a firewall management device for OPNsense.
* My OPNsense firewall appliance has a USB port for keyboard and a VGA port for a monitor.
* The swap file in OPNsense (console displayed error message onto the VGA display running pfTop) shows that the FreeBSD swap file for OPNsense kept expanding in one execution until the swap space filled up.
* A Windows 10 laptop executing the Pale Moon browser is able to run as expected the  Lobby  and  Firewall:Log Files:Live View  displays.  Missing is a display of the swap file size.  The graphics now work smoothly in 24.7.2. 

The pre-24.7 lobby displayed memory status (disk,ram,swap) in text - please return this display capability as an option.

With 24.7.2, there apparently is a memory leak.  Eventually, OPNsense reboots itself automatically.  The VGA console display presents a Login prompt (and a corresponding login needs to be done for the GUI OPNsense management interface).

I noticed that in System: Settings: Miscellaneous, the Swap File setting to "add a 2GB swap file to the system" was unchecked.  It is unclear whether a 24.7.x update disabled my swap file settings, I remember having an 8GB swap file for my OPNsense appliance.

When the swap file fills up (or is not established by a setting), it would be nice to have a more elegant way to add more swap space dynamically as well as a FYI message as part of the login messages displayed why an automatic restart was done by OPNsense (such as the swap file filing up).

It is possible that when the blocklists are being processed that invariably the swap file space will fill up (my configuration is 4GB Ram, 8GB swap space).   It seems that blocklist processing under 24.7.2 (Hagezi specifically) has never successfully completed since I applied the 24.7.2 changes.  OPNsense is also creating multiple history backups (every 2-3 minutes!) while processing the blocklists - so I have lost my original configuration backups (my generous backup of count of 2048 means that OPNsense has trashed all of my pre 24.7 history backups and has used up 30% of my disk space for useless history backups).   While processing blocklists, there is no need for interim history backups!!!

It would be very helpful to add a 14th option to the console selection menu:
14)  Display status of settings for RAM, Swap Space, Disk Space

I am disabling my usage of Hagezi block lists until the 24.7.x problems are sorted out.

Quote from: NonGough on August 27, 2024, 04:44:15 AM
I am disabling my usage of Hagezi block lists until the 24.7.x problems are sorted out.

Hello. If you mean these https://github.com/hagezi/dns-blocklists which are anywhere from many MBs to tens of MBs, then your solution is not swap but adequate hardware or not using such lists.

That said, you are absolutely off-topic here.

Grep memory /var/run/dnesg.boot   displays:
agp0: aperture size is 256M, detected 8188k stolen memory
pid 69794 (pftop), jid 0, uid 0, was killed: failed to reclaim memory

These messages started appearing with an upgrade to 24.7 and first noticed with an upgrade to 24.7.2 (even with the cessation of Hagezi blocklist processing).  Note that Hagezi blocklist processing (as a background task) pre-24.7 took less than an hour to always complete.

Not feeling like wasting more time arguing the obvious (as you can see, you are getting things on your box killed by OOM). Insist on using those lists? Use them with BIND. No python parsing nonsense needed.

https://github.com/hagezi/dns-blocklists/tree/main/rpz

Now, kindly stop hijacking this thread for absolutely unrelated issues.

Let's all take a break please. Failing widgets topics only here now. :)


Cheers,
Franco

For your information I got crash for widget after upgrade 24.7.2 commit 8ffbc6387.


Here the log console js :

opnsense_widget_manager.js?v=f55a118244ec13ff:148 Failed to load one or more widgets: (23) [TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w...]
(anonymous) @ opnsense_widget_manager.js?v=f55a118244ec13ff:148
await in (anonymous)
e @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
t @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
setTimeout
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fire @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
l @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
load
send @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
ajax @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
_loadWidgets @ opnsense_widget_manager.js?v=f55a118244ec13ff:122
initialize @ opnsense_widget_manager.js?v=f55a118244ec13ff:109
(anonymous) @ dashboard:1362
e @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
t @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
setTimeout
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fire @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
ready @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
B @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2Understand this error
opnsense_widget_manager.js?v=f55a118244ec13ff:117 Failed initializing Widgets Error: No widgets loaded
    at WidgetManager._initializeWidgets (opnsense_widget_manager.js?v=f55a118244ec13ff:154:19)
    at WidgetManager.initialize (opnsense_widget_manager.js?v=f55a118244ec13ff:111:18)


I used VM with speficiation

4 vcpu
8 GB RAM


Thank you Team

Yes it's your browser and it should be fixed in 24.7.3 anyway.


Cheers,
Franco