The new services widget is really good. One minor suggestion: please add a "Services" text header and an orange line to the top of the widget so that it matches every other widget.
Hi,
It was considered and you can still see the header during edit, but it takes a lot of space, especially on wide horizontal mode.
Using all available space was the main reason it was reworked.
Cheers,
Franco
All good. I still like it. My slightly OCD nature prefers consistency over precision/purpose.
I mostly feel the same about strong consistency and tried both, yet the main objective was to save space with the tile layout. :)
Cheers,
Franco
If you want to save space how about placing the widget tile centered on top of the orange line, for all widgets ?
In addition to I've noticed a scroll bar in single column mode even if I dragged the table down completely.
Quote from: Wrigleys on July 12, 2026, 12:19:34 PMIn addition to I've noticed a scroll bar in single column mode even if I dragged the table down completely.
To be honest :
I have noticed this kind of stuff in earlier OPNsense releases with some widgets and could not care less about it since it's not something I am looking at all the time and might also have to do with compatibility with the various browsers I am using :)
This is another example : https://forum.opnsense.org/index.php?msg=270100
"Oh well..."
As far as the scroll bar goes if you edit and expand and save it will use that size then...
Cheers,
Franco
the colour scheme for the services widget is just off compared to the rest of the theme now. Doesn't seem to matter what theme I pick even the standard opnsense theme.
The idea of Green background with black text to indicate a running service is fine but it just doesn't match the theme now. I hope @marjohn56 can work his magic on the Rebellion them.
Bonsoir monsieur Kev :D
To some extend it's true, but then again this perfectly aligns with theme colouring because we're using the theme's success and danger bootstrap colours so the themes can be tweaked to match better.
FWIW, I made a small change here to use the button style instead of the alert style which mutes the colours a little and follows the theme's style on whether to use light or dark text+symbols on it:
# opnsense-patch https://github.com/opnsense/core/commit/ace8f12f51
Cheers,
Franco
Upgraded to 26.7 without any issues, thanks for the clear release notes (Removed os-cpu-microcode-intel). Congratulations on the new version and thank you for all your hard work!!
I came here because the services widget looked be broken with the way it was rendering after the upgrade. It turned all black and white vs the nice colored status we had before that blended into the theme. Running vicuna theme here.
(link due to hard limit on attachments)
https://www.pasteboard.co/8JSLaKo_fJJ7.png
I tried the patch from this thread, but it made it worse.
(link due to hard limit on attachments)
https://www.pasteboard.co/4O3RNGbMbuOl.png
Is there any way to get the pre-upgrade colors back that seamlessly blended in using the super modern looking theme vicuna?
For reference, here is the pre-upgrade that blended well.
5.png
Thanks.
@Franco: Thanks for the effort that went into the new design, but I have to admit that I'm not a fan of it in its current form. It feels quite different from the overall look and feel of the interface, service names are now truncated, and the descriptions are no longer visible.
Personally, I find the previous design more practical and easier to read. Hopefully, this change can either be reconsidered, refined, or at least offered as an optional alternative rather than becoming the default for all widgets.
No offense intended—this is simply my personal feedback as a user. I appreciate the work that goes into OPNsense, but for me, this particular change does not feel like an improvement.
Back to the Roots...
Couldn't find any errors, but as always, use at your own risk!
For those who don't want that, here is the good view:
1. Login SSH
2. Press 8 for Shell
3. sudo nano /usr/local/opnsense/www/js/widgets/Services.js
4. Copy Contents in Services.js
https://github.com/opnsense/core/blob/stable/26.1/src/opnsense/www/js/widgets/Services.js
5. Reboot
Quote from: franco on July 18, 2026, 12:47:35 AMBonsoir monsieur Kev :D
To some extend it's true, but then again this perfectly aligns with theme colouring because we're using the theme's success and danger bootstrap colours so the themes can be tweaked to match better.
FWIW, I made a small change here to use the button style instead of the alert style which mutes the colours a little and follows the theme's style on whether to use light or dark text+symbols on it:
# opnsense-patch https://github.com/opnsense/core/commit/ace8f12f51
Cheers,
Franco
Merci Mon Amie
Thanks to one of the users above I found the rebellion theme and on 26.7 it looks much better than vicuna regarding Services Widget. Still, it's not as blended into the panel as before, but livable. It's not like I have to look at it all day every day. :) I do certainly prefer the old seamless look of vicuna shown in my earlier screenshots, but I'm just super happy that 26.7 is working well and all things stable.
6.png
Still hate it. Can I get black text on white background and a single icon in green or red back? Every other widget works that way: Interfaces, Gateways, WireGuard, ...
Plus with now two or three columns depending on the width of my browser window it takes way longer to find something. With the old widget I scanned one vertical list, alphabetically sorted, and that was that.
Please ... talk to a UX specialist. This does save space. But it's not good.
I didnt think of this, awesome recommendation, thank you.
Quote from: Mabub on July 21, 2026, 09:05:22 AM@Franco: Thanks for the effort that went into the new design, but I have to admit that I'm not a fan of it in its current form. It feels quite different from the overall look and feel of the interface, service names are now truncated, and the descriptions are no longer visible.
Personally, I find the previous design more practical and easier to read. Hopefully, this change can either be reconsidered, refined, or at least offered as an optional alternative rather than becoming the default for all widgets.
No offense intended—this is simply my personal feedback as a user. I appreciate the work that goes into OPNsense, but for me, this particular change does not feel like an improvement.
Back to the Roots...
Couldn't find any errors, but as always, use at your own risk!
For those who don't want that, here is the good view:
1. Login SSH
2. Press 8 for Shell
3. sudo nano /usr/local/opnsense/www/js/widgets/Services.js
4. Copy Contents in Services.js
https://github.com/opnsense/core/blob/stable/26.1/src/opnsense/www/js/widgets/Services.js
5. Reboot
Quote from: Mabub on July 21, 2026, 09:05:22 AM1. Login SSH
2. Press 8 for Shell
3. sudo nano /usr/local/opnsense/www/js/widgets/Services.js
4. Copy Contents in Services.js
https://github.com/opnsense/core/blob/stable/26.1/src/opnsense/www/js/widgets/Services.js
5. Reboot
Thank you very much for this tip!
Hi Team
Just some feedback on 26.7.1, the upgrade went fine, but I'm using the vicuna theme and the services widget is pretty much unreadable.
Hope you can fix it at some stage
Tbh, not sure if anyone asked for this change and why this wasnt pushed back against during the RC versions (if it was already implemented there)
The old list was easy on the eyes and has distinct separate parts (aka.. name | controls). And depending on the dashboard space, the list is mostly to long anyway so you need to scroll meaning it has your attention regardless without needing a lot of color.
This is basically someone saying: Ow no, I cant figure out if my hardware isnt running as its only a red light blinking. Lets make it so that when my hardware doesnt work it changes the color of my entire wall. And hides the power button somewhere on that wall as well.
Let's give the community themes a chance to fix their branding colors first, which is the core complaint here.
Cheers,
Franco
Quote from: franco on July 23, 2026, 12:16:03 PMLet's give the community themes a chance to fix their branding colors first, which is the core complaint here.
Is it really, though? A number of us, in the various threads discussing the same issue (sigh) have commented that the style just doesn't match that of the other widgets available on the dashboard, where status is represented by an LED-like icon to the left of the entity name, and not the background colour of the whole table cell. You can fiddle with colours all day, but IMO it's still going to look completely out of place.
Yes it all bloats the service widget back up to where it should have not been.
I find half the criticism valid and the other half misplaced (because the complaint is about the colors in the theme and people say it's "ugly" without doing the work necessary or trying to understand -- it's not a community trait I want to foster).
Also, several people said they like it which rarely happens when we do nice things and you all know that's true. ;)
My main concern with the argument "it doesn't fit" is that it is backwards-oriented when clearly this is all simple Bootstrap theming.
Are we at the point where we don't tolerate innovation? Just a few things I've been thinking about.
Cheers,
Franco
I hope I'm not coming across as belligerent about this - I'm just sharing my opinion. As I said somewhere, in one of the threads, I do like the compactness, but the style just doesn't work for me - it looks like something from a 1990's GUI that got shoved into a webUI that's otherwise fairly contemporary. The fact that it doesn't work for me personally isn't of great significance, but I got the sense that others see it this way too...
Some do, some don't.
Maybe lose the green inverse video effect and just color the text red/green depending on the service state.
Quote from: dseven on July 23, 2026, 01:24:47 PMit looks like something from a 1990's GUI
There are many cases of poor webdesign on the internet nowadays where I wish they had used good old '90's webdesign instead of modern crap that's ugly/bloated/disfunctional to be honest :P
But however I look at it : This new Services widget is not one of those cases!
OK, concrete points:
- the contrast of white text on light/medium green is bad
- the labels are truncated
- depending on the width of my browser window the number of columns changes - meaning "things move around"
All of this is bad UX, IMHO. It is way harder to find things compared with the old widget. Yes, the old one needed a lot of vertical space. I simply reserved an entire column just for that.
Quote from: franco on July 23, 2026, 01:03:53 PMYes it all bloats the service widget back up to where it should have not been.
I find half the criticism valid and the other half misplaced (because the complaint is about the colors in the theme and people say it's "ugly" without doing the work necessary or trying to understand -- it's not a community trait I want to foster).
Also, several people said they like it which rarely happens when we do nice things and you all know that's true. ;)
My main concern with the argument "it doesn't fit" is that it is backwards-oriented when clearly this is all simple Bootstrap theming.
Are we at the point where we don't tolerate innovation? Just a few things I've been thinking about.
Cheers,
Franco
Hello Franco,
This is childish behavior — only wanting to accept and defend what you personally like. I mean, many people have valid reasons for saying that it does not look good, not because of the colors or the theme itself, but because of the overall design. When you look at the rest of the GUI, it feels isolated and out of place compared to everything else.
Just my two cents. Nobody is against improvements, but criticism should also be acknowledged instead of being dismissed by saying, "Well, some people like it too." That is not a valid argument.
It also appears that you are the only one bothered by the fact that it is too big—without being able to give a plausible reason for it. It is simply supposed to be smaller—but why? No one had a problem with it before; I haven't read anything about that. Has there been any feedback or discussion thread indicating that it is too large and causing issues?
A reasonable compromise would be to make it optional. Think about it. This is not meant in a hostile way, but rather as a constructive suggestion.
Best regards
> This is childish behavior
Never mind me wanting to have a productive exchange and engaging the discussion head on.
We're done here if we're continuing ad hominem.
Cheers,
Franco
I prioritize core function over looks, so I'm not going to die on this hill, lol. It's a widget people, let's settle down.... But my last point will be that in vicuna, the old widget was beautiful and blended right in. Simple, clean, clear, not overbearing in-your-face colors, and the small green buttons elegantly indicated running vs the small red buttons indicating stopped were nothing short of UX genius....
With that said, (and only because of this change), that I noticed in my screenshot there does look to be some opportunity to optimize the space it took up without impacting the UI visuals. So if anyone ever takes a vote, I'm voting for the old clean and clear look, but then just optimize the space if we want to change something. As you can see in my screenshot, there's a country mile between the text and the green buttons. Win win! Innovation is great and I am truly glad the devs are thinking about how to optimize space.
Or, even just leave it like it was... It was the last thing I expected to change in this update, and honestly didn't even know there was a need before this update. Let's be honest, you only open the page to check the services if something isn't working, then you close the page and move on with life.... It's NOT like you really need to push those buttons all day long and need an OMG Optimized interface to operate them. :)
There's a ticket here since a week BTW, which certainly shows how childish I am. Lucky for me nobody posted anything there. So much for community being ignored and yearning for cooperation which was ultimately denied on a ticket from 2024 that only one member ever participated on. I'm hoping the irony here is clear.
https://github.com/opnsense/core/issues/10553
There's a POC now but I hate it. It's boring, bloated and much less obvious. Change my mind I guess?
This is YOUR project at the end of the day. Giving anyone a hard time for helping you is NOT the way of this community. I did not enjoy the interactions so far and I expect we can do better than that then.
Cheers,
Franco
Quote from: franco on July 23, 2026, 08:46:32 PMThere's a ticket here since a week BTW,
I somehow missed the memo. Find my comments there. And thanks! That's great.
Hello Franco,
This is by no means a personal attack; it simply describes the impression created by the response. I think it may have been misunderstood.
Please consider the entire post. I see a lot of suggestions for improvement here, and it would be wrong to focus only on the title. Criticism should be allowed and taken into account, because that is the only way a project can improve. That is something I feel is missing a little here.
Criticism is a natural part of any project and something that has to be accepted and dealt with constructively.
Have a nice day.
Quote from: Mabub on July 23, 2026, 09:14:40 PMI think it may have been misunderstood.
Please consider the entire post.
Completely agree, and please consider those of us trying to help with suggestions.
@Franco, #10553 above is brilliant! Thank you!
> Criticism is a natural part of any project and something that has to be accepted and dealt with constructively.
It has to be a pretty big misunderstanding.
Which part of https://github.com/opnsense/core/issues/10553 made it seem like I wasn't listening last week already?
Which part of https://github.com/opnsense/core/issues/7887 made it seem like we didn't want feedback from the community since 2024 about the subject?
Cheers,
Franco
Quote from: franco on July 23, 2026, 09:30:59 PMWhich part of https://github.com/opnsense/core/issues/7887 made it seem like we didn't want feedback from the community since 2024 about the subject?
I never noticed any discussion of this on the forum and I do not follow Github unless I open an issue or a merge request. First time I saw this: today.
Also I still do not quite understand what was bad about the old widget. But then I never work from mobile devices. "Working" means I am at my desk with a real keyboard and a reasonably sized monitor and I design all my dashboards of all products I use for that environment alone. Resolution of a Macbook Pro is large enough to not notice much of a difference when e.g. traveling.
Was that the initial motivation? Smaller screens? But then the entire dashboard is not specifically mobile friendly, so I'm still a bit puzzled why this effort was made at all. It is/was a long list. So be it :-)
Kind regards,
Patrick
Patrick, I addressed your concerns here: https://github.com/opnsense/core/issues/10553#issuecomment-5062751182
> I never noticed any discussion of this on the forum and I do not follow Github unless I open an issue or a merge request. First time I saw this: today.
I keep thinking how this is similar to the prologue of Hitchhiker's Guide but I fail to see that this wasn't publicly available information anyone from Earth could have reached in time. Besides it certainly isn't the end of the world as we know it. ;)
Cheers,
Franco
Quote from: franco on July 23, 2026, 09:58:33 PMI keep thinking how this is similar to the prologue of Hitchhiker's Guide but I fail to see that this wasn't publicly available information anyone from Earth could have reached in time. ;)
Beware of the leopard! :-)
I prefer the new widget in part because I rarely have need to check the Dashboard, so do not have a firm mental image from which to see discrepancies immediately. I experienced that problem recently in the old columnar widget, where the fact a service was off (hence a problem) did not stand out. With the new widget it is clear at once.
I also prefer not to have to scroll merely to check states rather than when reading text. Any warning should be visible immediately so again, the new widget wins. I try not to clutter my Dashboard, and with the new widget and some other rearrangements it is single screen, organised and clear on a large display or a Macbook Air.
It may have helped in my case that my theme is opnsense-dark where it seems to fit quite well, so I was not triggered by unexpected contrast. In any case I tend to run with low screen brightness and contrast. I can see from some other people's screenshots that in other contexts the display tones may need tuning.
Adding this by way of explanation rather than merely sitting back happily.
The old one wasn't consistent, either: it used the "play" and "stop" icons for its status display (instead of being actionable buttons as convention makes one expect). I've always wondered why it doesn't use the same status indicator as the ddns and the gateway widget (a colored dot, but sadly its size is not consistent: the dot in the gateway monitor is much smaller than the one in the ddns widget). So the new version is more logical / expectation-consistent than the old one, which is always a plus.
To me, the smaller height of the individual lines is welcome, and the full-line coloring could possibly be toned down into coloring only the part that contains the controls? (BTW, where did the start / stop go? I can only judge from the provided screenshots ATM though, maybe they've been moved).
Coloring the entire line will, if extended to the entire the GUI, end up coloring most parts of the screen in green, which defeats the purpose of a dark theme at least, and will probably be harder on the eyes all in all, and may end up looking cluttered / toy-like?
The ddns widget could use an overhaul as well though, to display the type and name in one line as it does ATM, but to then display the IP address and update time as full line each, instead of cutting it off at the same boundary as the type. The current way is OK for IPv4, but breaks with IPv6. Maybe this is already fixed in the new release already?
Also, the header isn't displayed for the "image" widget either, so it's not entirely unusual. Maybe the header itself could be shrunk for the all widgets, to remove the unnecessary empty space below the orange line, like it is done with the memory, disk, CPU, ddns and some other widgets?
Hi there,
after seeing the new widget for some day, I now just removed it because I'm just getting angry seeing this (anger issues..)
I really appreciate the work from the folks making this project possible.
But what I don't understand, why there is no chance for the user to choose from both versions.
There was obviously a working code for the old widget - and nearly all widgets have that little Pen-Symbol - why not add the pen and let users choose?
This would simply end all discussions, and allthough I know this a bit (but I think not too much) extra work.
Style "Classic" for the old one and "Compact" for the new one.
I also don't really understand where this goes? Should I expect all UI Elements to be cut down to the basic, even without headline?
For me, OPN-Sense had the most beautiful/functional Mix of the Interface for a long time.
Now I'm desperate, because if this "compacting" goes further, I know my experience is new anger with every update.
Most people have huge screens, and I really don't see functional benefit in compacting things, and IMO, it looks less modern, more like a bare HTML.
I would even make a 200€ donation to bring this widget back or implement the "Style-Pen-Function"!
Best regards
@JohnSchnee try:
opnsense-patch https://github.com/opnsense/core/commit/9412fa3bd8
Reference: https://github.com/opnsense/core/issues/10553
Quote from: JohnSchnee on July 27, 2026, 11:32:02 AMMost people have huge screens, and I really don't see functional benefit in compacting things, and IMO, it looks less modern, more like a bare HTML.
I don't feel like spending money in these expensive times to buy one of those weird Ultra HD monitors that most people use with something like 200% scaling because otherwise they need to buy a 42 inch monitor a.k.a. TV instead of a regular 22/24/27 inch monitor with 1080p/1200p/1440p resolution to be able to use it properly... LOL!!! :P
Not to mention websites where zooming OUT more than 1 time is getting mandatory more and more these days because of the same "Scaling People" who don't seem to understand what they are doing...
#SillyWorldWeAreLivingIn!
Sorry guys, i was on holiday :-)
Cicada and Vicuna Service widget color fix
https://github.com/opnsense/plugins/pull/5584 (https://github.com/opnsense/plugins/pull/5584)
@franco
Patch looks great now, thank you sir.
Yes, the design of the service box is okay, but it could be better. I'm also not entirely sure why the "button" class was used for the service widget. But okay—what is strange, though, is that the service widget's heading is missing. It is visible in edit mode, however. Is that intentional?
Quote from: opnsenseuser on July 28, 2026, 08:25:04 AMthe service widget's heading is missing. It is visible in edit mode, however. Is that intentional?
It seems to be intentional for maximum compactness. It was the first thing that threw me off, because in a dark theme, it kindof looks like the services table is part of the widget above.
so i changed the colors again, because this didn´t fit.
but the service widget needs the header i think
it would look like this with the header for vicuna and cicada
only the alert service´s are in red.
I find that it doesn't look so cluttered in terms of color, and appears calmer.
Request: https://github.com/opnsense/plugins/pull/5584
I think the service widgets should have a unified design, if only for the sake of clarity.
Quote from: opnsenseuser on July 28, 2026, 09:03:25 AMI find that it doesn't look so cluttered in terms of color, and appears calmer.
Agreed. It's still not following the UX of the other widgets (where there's a LED-like icon to show the status of the "thing"), but as a compromise between compactness and visual appeal, this does look a lot better to me...
Quote from: dseven on July 28, 2026, 08:42:47 AMQuote from: opnsenseuser on July 28, 2026, 08:25:04 AMthe service widget's heading is missing. It is visible in edit mode, however. Is that intentional?
It seems to be intentional for maximum compactness. It was the first thing that threw me off, because in a dark theme, it kindof looks like the services table is part of the widget above.
That doesn't make sense to me. Because when I look at the WOL widget, it takes up just as much space as the service widget ;-)
But that's a line break problem.
The DHCP widget could also save a considerable amount of vertical space if the IP address and hostname were on the same line instead of separated.
would be a simple solution for the dhcp widget.
It would all be in one line, much clearer and tidier, and above all, more space-saving.
see screenshot
There are other widgets too, that could be optimized in terms of space.
But it's quite clear to me that the service widget needs a heading.
Quote from: opnsenseuser on July 28, 2026, 10:20:08 AMIt would all be in one line, much clearer and tidier, and above all, more space-saving.
I suspect (don't know) that they went after the Services widget first because it was the biggest offender in terms of space wastage (you'd typically have a lot more Services than you'd have DHCP networks, etc.).
To properly align all the widget columns horizontally, you would need to use either JavaScript or different CSS classes, since the widgets have varying numbers of columns. However, it is possible and could save a lot of space.
Quote from: opnsenseuser on July 28, 2026, 10:07:01 AMThe DHCP widget could also save a considerable amount of vertical space if the IP address and hostname were on the same line instead of separated.
The wasted space needs to removed on this one :
(https://forum.opnsense.org/index.php?action=dlattach;attach=57091;image)
And then it's fine IMHO :)
This :
(https://forum.opnsense.org/index.php?action=dlattach;attach=57097;image)
Is not a real improvement when it comes to the wasted vertical space ;(
I'd like to see an option to exclude static leases for the Kea dashboard widget.
I have an Ultrwide monitor so my columns might be slightly larger than yours but my Kea DHCP Widget already lists the Devices and IPs side by side.
Quote from: nero355 on July 28, 2026, 05:30:17 PMThe wasted space needs to removed on this one :
(https://forum.opnsense.org/index.php?action=dlattach;attach=57091;image)
And then it's fine IMHO :)
At least the text is readable entirely, contrary to the ddns widget, which should use the full line for the IP instead of only the first column, and also should line-break the IP if it doesn't fit, like it does with the update time (compare how the "fe" (and all following hextets) is cut off while the "AM" is moved into the next line). The description "Current IP" could be put into the same line if it would line-break, to possibly save one line.
It seems to not have been used with IPv6 much yet. :)
If you stretch the individual widget to make it wider, the row also shifts upwards.
Yes, but there is so much space wasted and widening it even further creates the problem that all other widgets won't properly fit anywhere anymore unless I put the ddns widget at the top. And if I go to a smaller screen it'd break the layout even more.
There are some other possible improvements to the general GUI layout that I take this opportunity to propose:
1) Move the tab header into the top row, along with the "edit GUI" button. That will remove the entire tab height which is more or less just blank space.
2) Move the footer into the left column, since that seldom contains more than fits on a screen, and frees up the entire footer height in the main view.
3) Make the title of the "Firewall States" widget editable, or change it to something that fits in one column, like "States". This is not terribly important though.
4) Change the FW rule display into a horizontal bar graph like the thermal/sensors widget. That way the text can be inside the graph and not overlap. It'd need to have some form of color inversion / XOR to remain readable though, look at Zone 0 for how it should not end up being like. :)