Updated - first impressions

[Patrick M. Hausen]

Same here. I submitted the crash report. But this does not look like the known Nut segmentation fault but rather like a UI/Frontend problem.

[julsssark]

Thanks Patrick. I created an bug report: https://github.com/opnsense/core/issues/10534

[muchacha_grande]

The upgrade went fine here without problems... almost everything is working as expected.
One comment(1) and one caveat(2):
1. I'm with Patrick about the services widget. A proper header will not occupy much space and will make it more in line with the other widgets.
2. Accessing Nginx->Configuration page is crashing.

Code Select Expand

[15-Jul-2026 13:23:47 America/Argentina/Buenos_Aires] TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /var/lib/php/cache/_usr_local_opnsense_mvc_app_views_layout_partials_base_form.volt.php:9
Stack trace:
#0 [internal function]: Phalcon\Mvc\View\Engine\Volt->render('/usr/local/opns...', Array, false)
#1 [internal function]: Phalcon\Mvc\View->engineRender(Array, 'layout_partials...', false, false)
#2 [internal function]: Phalcon\Mvc\View->partial('layout_partials...', Array)
#3 /var/lib/php/cache/_usr_local_opnsense_mvc_app_views_layout_partials_base_tabs_content.volt.php(8): Phalcon\Mvc\View\Engine\AbstractEngine->partial('layout_partials...', Array)
#4 [internal function]: Phalcon\Mvc\View\Engine\Volt->render('/usr/local/opns...', Array, false)
#5 [internal function]: Phalcon\Mvc\View->engineRender(Array, 'layout_partials...', false, false)
#6 [internal function]: Phalcon\Mvc\View->partial('layout_partials...', Array)
#7 /var/lib/php/cache/_usr_local_opnsense_mvc_app_views_opnsense_nginx_index.volt.php(267): Phalcon\Mvc\View\Engine\AbstractEngine->partial('layout_partials...', Array)
#8 [internal function]: Phalcon\Mvc\View\Engine\Volt->render('/usr/local/opns...', Array, true)
#9 [internal function]: Phalcon\Mvc\View->engineRender(Array, 'OPNsense/Nginx/...', true)
#10 /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ControllerBase.php(151): Phalcon\Mvc\View->processRender('', '')
#11 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Dispatcher.php(168): OPNsense\Base\ControllerBase->afterExecuteRoute(NULL)
#12 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Router.php(156): OPNsense\Mvc\Dispatcher->dispatch(Object(OPNsense\Mvc\Request), Object(OPNsense\Mvc\Response), Object(OPNsense\Mvc\Session))
#13 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Router.php(139): OPNsense\Mvc\Router->performRequest(Object(OPNsense\Mvc\Dispatcher))
#14 /usr/local/opnsense/www/index.php(66): OPNsense\Mvc\Router->routeRequest('/ui/nginx', Array)
#15 {main}
EDIT: this looks like the exact same problem with the nut configuration page reported by julsssark

[Patrick M. Hausen]

That's the second one. Services > Nut > Configuration, too. I see a hotfix incoming 😉

[muchacha_grande]

Until a hotfix or 26.7.1 is released, opnsense-patch 14710e7 will fix the crash on Nginx, NUT and Squid menues

[Bob.Dig]

I am not sure about this one, so I am posting it here. I think I do see a higher RAM-usage. But I have no historical data and that VM has only 1 Gig of RAM to begin with (UFS).
Right now, after a reboot, it looks okayish. Maybe others have better data.

 

[sopex]

I am not sure about this one, so I am posting it here. I think I do see a higher RAM-usage. But I have no historical data and that VM has only 1 Gig of RAM to begin with.
Right now, after a reboot, it looks okayish. Maybe others have better data.

 

Proxmox?

[seed]

@Patrick:
Can you confirm that DestNAT (IPv4) on your side? In my setup it did not work. I try to figure out if i have a config issue that still worked with 26.1.11_10 or if its version related.

[Patrick M. Hausen]

Can you confirm that DestNAT (IPv4) on your side?

Can you confirm that DestNAT ... does what, now?

[seed]

Sorry.
Can you confirm that DestNAT (IPv4) is working on your side?

[Patrick M. Hausen]

Yes, no problems.

[nero355]

I think I do see a higher RAM-usage.

But I have no historical data and that VM has only 1 Gig of RAM to begin with (UFS).

Your OPNsense VM only has 1 GB of RAM ?! How ?!

I have a dedicated Mini PC that happens to have 16 GB RAM because the previous owner bought it like that and my typical RAM useage for OPNsense is :
- Around 750 MB after a fresh reboot.
- Around 2 GB after running for some time and getting to an average operational state so to speak.

It has been like that now all the way up to 26.1.11_6 and I only use :
- Firewall
- NAT
- Routing
- DHCP
- 4 Interfaces :
igc0 - WAN - VLAN sub-interface with DHCP Client active.
igc1 - Default LAN
igc2 - Home Network
igc3 - Dedicated Assign VLANs Interface with for now just a Guest Network.

Total number of IP Addresses going through this is somewhere between 30 to 40 usually IIRC :)

[MoonbeamFrame]

Back to the services widget.

If the start, restart, stop objects were colour coded to follow the service status, e.g. green - when running, this would be consistent with other widgets. Then the cell back ground could follow the theme, except when a service is stopped when it would be set to red.

[tbt39]

The service widget is so bad I had to sign up to add another voice to this (which, y'know, speaks to how well it works otherwise).

It's just completely out of place and clashes style-wise with every other widget.
It's also pretty much broken in the Cicada theme.

Please re-think this and start from scratch if you really want to condense it.

[franco]

Well, themes need to be maintained. Got downvoted on a discussion about services widget on Reddit so please throw actual usable ideas around instead of saying it's really bad. There are people who really like it too and said so, which is way less common than people complaining :)

Improved the colouring a little with the below patch, but in the end the theme is fully in charge which was the main design point to avoid complains it looks silly in themes and can't be overridden by themes.

# opnsense-patch https://github.com/opnsense/core/commit/ace8f12f51


Cheers,
Franco