Messages

Just an update on this issue.

Following Aerowinder's suggestion that the issue might be related to a reverse proxy, I removed Nginx Proxy Manager from in front of OPNsense and the issue appears to have been resolved completely. Thanks to Aerowinder for pointing me in the right direction.

I have not tried disabling KTLS specifically, instead opting for the simpler approach of bypassing the proxy. Accessing OPNsense directly via its management hostname and port works as expected, and I have not been able to reproduce the missing UI elements or JavaScript issues since making this change.

Currently, it appears that the problem is related to the reverse proxy configuration rather than OPNsense itself.

Hi,

I upgraded from 26.1 to 26.7 yesterday and have encountered an issue with several pages in the web UI when using Chrome Version 150.0.7871.125 (Official Build) (arm64) on macOS.

The affected pages display the header and introductory text, but the data table never loads and the orange loading bar remains visible indefinitely.

Affected pages include:

* Services → Unbound DNS → Overrides → Host Overrides
* Firewall → Rules

Initially, the Firewall → Rules page was blank until I installed the os-firewall-legacy plugin, which restored access to the legacy rules interface.

The browser console shows the following error for Services → Unbound DNS → Overrides → Host Overrides:

ReferenceError: Tabulator is not defined

The issue persists in Chrome incognito mode. Opening the same pages in Firefox does not present the same issue, which suggests this may be related to Chrome rather than the OPNsense backend.

I verified that:

The tabulator.min.js file exists:

/usr/local/opnsense/www/js/tabulator.min.js
The file is served correctly by the web server:

curl -k https://10.50.99.1:666/ui/js/tabulator.min.js -o /tmp/tabulator-served.js

The SHA256 hashes match:

SHA256 (/tmp/tabulator-served.js) = 86df9b98a7cde1098d8cbc0f1916b6989971507984299bc0b4d289a63ed520a0
SHA256 (/usr/local/opnsense/www/js/tabulator.min.js) = 86df9b98a7cde1098d8cbc0f1916b6989971507984299bc0b4d289a63ed520a0

Additional information:

configctl unbound check reports no errors.
pfctl -sr confirms that all firewall rules remain loaded and active.
Restarting the web GUI and clearing browser cache/site data did not resolve the issue.
Installing os-firewall-legacy restored access to the firewall rules UI.

Environment:

OPNsense 26.7
Chrome Version 150.0.7871.125 (Official Build) (arm64)
macOS
Firefox unaffected
OPNsense accessed via a custom hostname on port 666

Has anyone else seen this behaviour with Chrome after upgrading to 26.7?