Messages

Hi,

I'm seeing the same thing on Hyper-V, though less frequently than described here.

Environment:

OPNsense 26.7.6-amd64, FreeBSD 15.1-RELEASE-p4, OpenSSL 3.5.9
Virtualized on Hyper-V (host CPU: AMD EPYC 4584PX), VM with 8 GB RAM
Unbound 1.26.1 (since 18/09), Python module with dnsbl_module loaded
[Upgraded to 26.7.6 on: ...]

What I observe:

Today, 2026-10-09 04:15:53, kernel log:
pid 19272 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)
The VM had rebooted at about 04:10 and Unbound started cleanly at 04:10:55. It crashed roughly 5 minutes later.
The resolver log shows nothing unusual before the crash. The last line is dnsbl_module: successfully opened pipe at 04:11:05, then silence until "Closing logger".
Earlier unclean death on 2026-10-04 at 03:01:31: the resolver log shows "Closing logger" without the usual "service stopped", and no restart afterwards. Unbound was apparently down until I rebooted on 2026-10-09 01:16, so about 5 days without DNS resolution from OPNsense. I can't confirm a signal 11 for that one, since my kernel log excerpt has no matching entry.
I restarted Unbound manually after noticing it was stopped on the dashboard.

I have not downgraded the kernel yet. Reverting to 26.7.5...

Thanks

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.

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

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

[Back to the Roots...Couldn't find any errors, but as always, use at your own risk!]

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

[Back to the Roots...Couldn't find any errors, but as always, use at your own risk!]

@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

... ok, dachte du hast vielleicht einen "direkteren Draht",  ich versuche mein Glück, Danke.

Man kann nur hoffen, dass es nicht weiterverfolgt und auch noch auf andere Widgets angewendet wird.

Ich hoffe, dass es rückgängig gemacht wird oder wenigstens nur optional bleibt.

Vielleicht kannst du das als Anregung weitergeben, Patrick.

Ok, das entzieht sich zwar jeder Logik, da man das Fenster in der Größe ohnehin anpassen konnte.
Auch fehlt der Titel nach dem Editieren der Oberfläche – ob das Sinn macht/gewollt ist!?
Eine Auswahl, welches Widget man möchte, wäre die bessere Lösung gewesen. Man muss sich damit wohl abfinden. Es passt überhaupt nicht ins Gesamtbild.

Leider in jedem Theme das gleiche Problem... ich gehe mal nicht davon aus, das es so aussehen soll?

Edit: OMG ... ich vermute fast, dass es doch so ist. Für den Fall: Was hat einen dazu bewegt, es schlechter zu machen?

Moin zusammen,

ich habe seit dem Update auf 26.7 einen Anzeigefehler im Dashboard (Dienste). Den Browser-Cache habe ich bereits geleert. Kann das jemand bestätigen?

OPNsense 26.7-amd64
FreeBSD 15.1-RELEASE-p1
OpenSSL 3.5.7

Firefox 152.06

Für alle die sich daran stören und nicht warten wollen, kleine Anleitung zur Fehlerbehebung:

Achtung: Nutzung auf eigene Gefahr, bitte vorher immer Backup machen!

Code Select Expand

# Putty zu OPNsense... anmelden... (8)Shell...
pkg install gettext-tools
cd /usr/local/share/locale/de_DE/LC_MESSAGES/
msgunfmt OPNsense.mo -o OPNsense.po
pkg install nano
sudo nano OPNsense.po
# (STRG+W) RSA-3072 suchen... editieren... (STRG+O) speichern und verlassen
msgfmt OPNsense.po -o OPNsense.mo
service configd restart
configctl webgui restartggf. reboot... fertig.

OPNsense 26.1.1-amd64
FreeBSD 14.3-RELEASE-p8
OpenSSL 3.0.19

Hallo zusammen, in der aktuellen Version (egal wo) ist der Schlüsseltyp RSA 3072 im Dropdown-Menü 2x aufgeführt, ich glaube der 2048 fehlt oder ist falsch beschrieben. Hab nur ich das? .... Es scheint in der "Deutsch" Übersetzung falsch zu sein, auf Englisch stimmt es... einmal EDIT bitte ^^

Patrick, danke für die Info. :)

Hallo zusammen,

This component is reaching the end of the line, official maintenance will end as of version 26.1

diese Meldung erscheint unter:

    VPN: OpenVPN: Servers [legacy]
    VPN: OpenVPN: Clients [legacy]

openvpn 2.6.13
opnsense 25.1.2

Wird dann nur die aktuelle Version von OpenVPN 2.6.13 nicht mehr unterstützt oder wird es generell kein OpenVPN in OPNsense mehr geben?
Leider habe ich noch keine weiteren Infos dazu gefunden und frage daher mal hier nach.

Grüße

Alles klar. Dann nochmal vielen Dank an euch. 8)