Messages

2) The guy has spent the last 15 years as a generic IT guy in marketing organizations.

This is the key: "Marketing"

May be related to Monit package update to 6.0.0... https://mmonit.com/monit/changes/

Unbelievable... doesn't make any sense.

Coincidentally this video was published today https://youtu.be/a3RI4DjFBzw

Awesome. It can't be better... wow!!

We all know how much time it takes for a project like this to get mature... if it started recently and suddenly it has all the features, I would say that it is likely completely AI coded.
Having said that, I also think that AI in good and responsible hands is "the tool" for coding but it will take time for this FW to reach a mature state as OPNSense has reached already.

Hi MiRei, the two patches that solves the Security Headers modal dialog are:

opnsense-patch -c plugins 1726d9e
opnsense-patch -c plugins 9ee2cd4

The patch that you applied is the one that solved the first problem found on Nginx plugin in version 26.7.0 that crashed when you accessed to the configuration menu.
If you applied opnsense-patch 14710e7 after updating to 26.7.1_1 then you broke Nginx again because that patch was already applied in 26.7.1_1 version.
Because of the way patches work, they are disabled if applied a second time, so applying 14710e7 over 26.7.1_1 is a regression.

Now, to recover your system to 26.7.1_1 version, you have to apply opnsense-patch 14710e7 again. An then, if you want to test the upcoming Security Header UI patch you can apply the other two patches I mentioned above, 1726d9e and 9ee2cd4.

I don't think that this is a specific problem to .lan domain. Don't rename it.
Just uncheck the option "Harden Below NXDOMAIN" and test it for some time to see if it works as you need.

It's in Services: Unbound DNS: Advanced. The fifth option.

Hi Timeraider, I've reported this issue on github https://github.com/opnsense/core/issues/10546.
Another issue reported earlier that can be related is https://github.com/opnsense/core/issues/10535. This has been already addressed but Franco reopened it because there is a chance that it is also related to this problem.

This window (Edit Security Header) has folder tabs.
I've been navigating through every menu and edit window and didn't find other edit window that has folder tabs inside.

I've found another problem with Nginx pages. I can't access HTTP(S)->Security Headers.
I created an issue at https://github.com/opnsense/core/issues/10546#issue-4903753570

@Timeraider, @Stinky-Packets, can you confirm if you have access to this page. The Edit Security Header page only shows empty tabs.

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

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

@franco, I was at 26.1.10 and noted this behavior. The first part of the update were fine and I could see all the packages update progress.
When it reached the point to update kernel and base packages it stuck a while until it showed kernel download complete, and then stuck again until base download complete.
After that, the update continued as normal, with kernel and base installation and reboot.

It was the kernel and base download that I couldn't see the progress, so depending on the download speed one could think that the update stopped.