Hi all,
thanks to the team for the great work! Friction between OPNsense and upstream FreeBSD aside 15.1 is a big step forward for both projects.
- The update showed no major problems here.
- The mimugmail-single repo is not yet up to the new ${ABI}, but the old binaries still work, no service outage whatsoever.
- Nut is finally working again with the default packages.
- To get a consistent view of the plugins I needed to completely disable the mimugmail-single repo, perform "pkg update", then they switched from "orphaned" to "installed".
- I don't like the look of the new services widget. Like at all, sticks out like a sore thumb. But I can live with it. At least please put a proper header on it as someone else already suggested.
Again: double thumbs up!
Patrick
Hey,
I will join too, even though I did not yet upgrade to the official Major, but I did test the RCs.
- It is true that the new service widget is sticking out - its too eye candy, but I kinda like it due to 2 reasons:
* Its eye poking so its hard to miss something is down
* It takes less space compared to the old one
- The new Interfaces pane of view is a welcome change, its more consistent with the overall style
- The Additional MVC/API integrations - hell yea!
- Adjustments on the Live log widget, this is already there prior the Major, but I would like to still thank for it, its awesome
Thank you all for the hard work and I am personally glad we landed on FBSD 15.1!
Regards,
S.
Hi Patrick,
Thanks for your fast feedback. :)
>- The mimugmail-single repo is not yet up to the new ${ABI}, but the old binaries still work, no service outage whatsoever.
Michael was working on it this week. Hoping to see it up shortly.
>- Nut is finally working again with the default packages.
That's nice to hear!
>- To get a consistent view of the plugins I needed to completely disable the mimugmail-single repo, perform "pkg update", then they switched from "orphaned" to "installed".
Yep, this is expected. Faulty repositories should always be removed.
> - I don't like the look of the new services widget. Like at all, sticks out like a sore thumb. But I can live with it. At least please put a proper header on it as someone else already suggested.
The colours can be changed per theme. We wanted to wait a bit and see which other complains are coming up. I'm not a fan of the header for available space reasons so maybe we can find another way to make it more obvious.
Cheers,
Franco
I am with Patrick regarding the new services widget. It just doesnt' fit with the rest of the gui.
For the widget it would be better if only the borders were colored per each process per state.
Regards,
S.
Hum, the latest service widget appearance was far better as my "home" is on 4 columns, the last one dedicated for services list ... well, not a big deal, upgrade was smooth, thanks
Quote from: franco on July 15, 2026, 01:11:22 PMI'm not a fan of the header for available space reasons so maybe we can find another way to make it more obvious.
I'd like it to look more consistent with the rest of the widgets.
I also never liked the not quite so new dashboard for the simple reason that the widgets do not snap to a fixed grid. Height should always be a multiple of X and vertical space between widgets should automatically create "lines" spanning multiple columns where appropriate. I hope you understand what I mean. I created an attachment. That's driving me up the walls. Honestly :-)
Kind regards,
Patrick
The design language of the widget is completely different from rest of the project.
That being said it's very space efficient and you can very easily identify what is enabled and what disabled.
I've updated successfully a few (ZFS) devices with various configurations, and also an APU4 running on UFS.
Big thanks to the team for the time and effort that went into this release.
Looking forward to seeing the OpenSSH 10.4 update in 26.7.x (was published too late to be included in 26.7)
Quote from: Patrick M. Hausen on July 15, 2026, 01:18:18 PMThat's driving me up the walls. Honestly :-)
me too :)
Regards,
S.
Well I'm happy the biggest "issue" is just a widget so far, lol. :)
Carrot 🥕 and stick ? Rally the masses against a common enemy and get away with everything else.
For 27.1 we'll have IPv6 and IPv8 only networks.
FWIW... I upgraded a test instance this morning, and my first reaction to the widget was "WTF is that?? Is it a glitch? Hmm, actually, it looks kindof useful, but ugly!". Without a header, at least in dark mode, it looks like it's (erroneously) part of the widget above.
Maybe just add an option? Simple checkbox "show header". Even with the header added the new widget saves so much space, I'd say mission accomplished.
Another thing that has been bugging me for years, but I'll open a request on Github: the CPU graph should be fixed to 100%.
I need to quickly discern:
- squiggly line at the bottom - I don't care if it's 3% or 11%, mostly idle is all the info I need
- 50%-ish
- at the top - ok, the CPU is maxed out, let's check if that is a problem or not
Autoscaling for CPU (or for any other limited capacity) does not make sense, IMHO. Memory, bandwidth, ... all the same. It should scale to the maximum that I have (16 GB, 1 Gbit/s, ...) so I can check with one glimpse how much of what I have is used.
Kind regards,
Patrick
@Patrick, can you get into Services->NUT->Configuration? I am seeing a crash when I try. I can get into Diagnostics and it shows my UPS status, so it appears that NUT is running. I tried uninstalling and reinstalling the NUT plugin, but that did not fix it.
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.
Thanks Patrick. I created an bug report: https://github.com/opnsense/core/issues/10534
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.
[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
That's the second one. Services > Nut > Configuration, too. I see a hotfix incoming 😉
Until a hotfix or 26.7.1 is released, opnsense-patch 14710e7 will fix the crash on Nginx, NUT and Squid menues
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.
Quote from: Bob.Dig on July 16, 2026, 04:42:38 PMI 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?
@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.
Quote from: seed on July 16, 2026, 05:14:18 PMCan you confirm that DestNAT (IPv4) on your side?
Can you confirm that DestNAT ... does what, now?
Sorry.
Can you confirm that DestNAT (IPv4) is working on your side?
Yes, no problems.
Quote from: Bob.Dig on July 16, 2026, 04:42:38 PMI 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 :)
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.
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.
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
That's fair. I'm not a designer, however, so apologies if I can't be more specific..
(https://i.ibb.co/RGQ05HP1/Screenshot-20260718-082957.png) (https://i.ibb.co/KcVq1y7Y/Screenshot-20260718-082957.png)
Using the opnsense theme for the sake of this, which I assume to be the default, and which I'd assume to be updated alongside changes like this (although it's not really any different in advance, rebellion and the mentioned cicada).
I'd think it's immediately obvious, but the widget is an entirely different style.
Every other widget has more spacing between elements in a very consistent logical fashion. Even widgets that do contain colors, the spacing and the shape help relax it.
The new service widget is just one big boxy block of color that looks out of place among the more elegant design of everything else (minus maybe the interfaced widget, but I fixed it in the dashboard editor just now by increasing the size once and then reducing it again, which hides the port information on narrower sizes correctly - EDIT: well, maybe not, a reload breaks it again).
The design and ease of use in the dashboard was something I always appreciated with opnsense (I have to deal with a large checkmk installation for work, I know bad dashboard design ;)).
Thanks for your feedback... the people nagging there's excessive padding everywhere are awfully quiet at the moment. To some degree it's funny trying to cater to this part of the user base and seeing a bit of backlash for it.
We can add padding, make it bigger, or we can leave it to acclimate. I'm unsure yet with the mixed signals.
But there's one fact of life here that the dashboard needs to be reorganized by people using widgets that are changed in design and people may just not like that about it. I'm keeping mental notes on the situation.
Cheers,
Franco
Count me in the apparent minority who think the new services widget is an improvement. I like it. For context I use Opnsense's dark theme.
I like that it's compact - I actually had removed the (old) widget from my dashboard because it just took up too much space.... but as others have noted, the new one just doesn't match the style of the rest of the dashboard, so it "sticks out like a sore thumb". As I commented in one several other threads about this (one that got hijacked for a Hyper-V discussion), a more in-keeping style would be to have a "LED" to the left of each item, with color indicating the status, rather than using the background of the whole "button"... but at the expense of a bit of "compactness"...
Quote from: passeri on July 18, 2026, 10:27:09 AMCount me in the apparent minority who think the new services widget is an improvement. I like it. For context I use Opnsense's dark theme.
I have to agree, I felt the old one took up too much space.
Also, would like to add the update to 26.7 went fine for me, aside from the minor issue with the nut configuration page which was fixed by the patch.
Congrats to the team. With other firewall software I used to feel the need to install updates to a new drive so I could keep the previous install intact in case something went wrong. With OPNsense I no longer feel the need to do this, just take a snapshot and proceed with the update.
Quote from: franco on July 18, 2026, 09:23:47 AMThanks for your feedback... the people nagging there's excessive padding everywhere are awfully quiet at the moment.
To some degree it's funny trying to cater to this part of the user base and seeing a bit of backlash for it.
We can add padding, make it bigger, or we can leave it to acclimate. I'm unsure yet with the mixed signals.
You could say I am one of those people in general, but the thing is : I am not much of a widget guy...
One possible explanation of that is because I have a bad image of it in my mind since Windows Vista and Android started using those damn things and I was always like : Why the hell would you use those things ?!
I know they have a totally different purpose for OPNsense and they are basically not widgets and something much more useful instead, but still I somehow can't really be bothered by them... Sorry! :)
So to make a long story short :
This =>
Quote from: tbt39 on July 18, 2026, 09:12:21 AMThat's fair. I'm not a designer, however, so apologies if I can't be more specific..
(https://i.ibb.co/RGQ05HP1/Screenshot-20260718-082957.png) (https://i.ibb.co/KcVq1y7Y/Screenshot-20260718-082957.png)
Is very nice and compact without wasting unnecessary screenspace so I like it and perhaps will consider Enabling it again in 26.7.x after upgrading ;)
The only possible improvement that I can think of is perhaps experimenting with a black line around the green (the button ?) and perhaps using white text with a small black edge around the same way it's used commonly for subtitles, but maybe it's not even needed in this case... dunno...
Ohh and I like this idea too by the way :
Quote from: dseven on July 18, 2026, 10:36:45 AMa more in-keeping style would be to have a "LED" to the left of each item, with color indicating the status, rather than using the background of the whole "button"... but at the expense of a bit of "compactness"...
Seen that many times in other software (both round and square "LEDs" ) and can look very good!
Quote from: Patrick M. Hausen on July 15, 2026, 01:04:08 PM- Nut is finally working again with the default packages.
Unfortunately, it's not for me. I had NUT previously installed using the latest OPN version prior to this one (26.1.11_10) but wasn't providing any diagnostic information, so I uninstalled it and did not revert to the previous version.
Rebooted prior to my 26.7 upgrade this morning after removing the intel-microcode plugin (after reading about the issues it was apparently causing during upgrade), and upgraded to 26.7 without issue.
So, I tried to install NUT after reading this post, and the configurations apparently remain even after uninstalling from yesterday, because the only thing that works is the diagnostics page. The configuration page throws an error which I sent the issue via the OPNSense report button off.
I have nothing outlandishly installed on OPN, so there is still an issue with this plugin that perhaps you can see with my config that I reported.
Edit: (Patrick, I didn't see the other posts past your acknowledgement of NUT issues, lol)
Quote from: julsssark on July 15, 2026, 04:49:18 PM@Patrick, can you get into Services->NUT->Configuration? I am seeing a crash when I try. I can get into Diagnostics and it shows my UPS status, so it appears that NUT is running. I tried uninstalling and reinstalling the NUT plugin, but that did not fix it.
Having the same issue (I just posted about above).
Quote from: franco on July 18, 2026, 12:50:48 AMWell, 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
My only issue with it is apparently theme-based colors, lol.
https://imgur.com/a/Lr8YMi9 (https://imgur.com/a/Lr8YMi9)
Quote from: Amodin on July 18, 2026, 06:40:07 PMQuote from: julsssark on July 15, 2026, 04:49:18 PM@Patrick, can you get into Services->NUT->Configuration? I am seeing a crash when I try. I can get into Diagnostics and it shows my UPS status, so it appears that NUT is running. I tried uninstalling and reinstalling the NUT plugin, but that did not fix it.
Having the same issue (I just posted about above).
opnsense-patch https://github.com/opnsense/core/commit/14710e7
Quote from: Amodin on July 18, 2026, 06:50:31 PMMy only issue with it is apparently theme-based colors, lol.
https://imgur.com/a/Lr8YMi9 (https://imgur.com/a/Lr8YMi9)
Yeah, this is an oversight more or less: https://forum.opnsense.org/index.php?topic=52451.0
We already use a a bit of brand-danger in the pages, but brand-success a lot less. Doesn't change the fact that these are normal bootstrap branding colors that should go nicely in every theme. If not it's easy to adjust them as it's just these two colors.
Quote from: muchacha_grande on July 16, 2026, 03:21:22 PMUntil a hotfix or 26.7.1 is released, opnsense-patch 14710e7 will fix the crash on Nginx, NUT and Squid menues
How do I apply this patch please?
Quote from: vk2him on July 18, 2026, 11:24:02 PMQuote from: muchacha_grande on July 16, 2026, 03:21:22 PMUntil a hotfix or 26.7.1 is released, opnsense-patch 14710e7 will fix the crash on Nginx, NUT and Squid menues
How do I apply this patch please?
By entering this command as the root user logged in to your firewall:
opnsense-patch https://github.com/opnsense/core/commit/14710e7
Logged in on the console or via SSH.
@ Patrick M. Hausen
I've applied the patch, so far so good :-)
one little thing, if you now change things in NGINX, you can not switch back to the "General Settings" tab, you need to reload the page from the side panel.
Many thanks
roman