OPNsense Forum

English Forums => 25.7, 25.10 Series => Topic started by: wallaby501 on January 16, 2026, 02:19:07 AM

Title: Unbound reporting not working on 25.7.10
Post by: wallaby501 on January 16, 2026, 02:19:07 AM
I could be wrong because I honestly did not know of this before this version but it's not working for me. I'm unsure if it's specific to this version or not.

I made sure I have no errors in the new blocklist features and I've reloaded it since then but have NOT rebooted yet.

I see "Cannot read properties of undefined (reading 'total')" in the dev tools on the page. I have let it go a couple hours since fixing the issues with dnsbl of unbound.

One thing I will note is that I store /var/log in RAM to avoid excessive writes to my NVME. Will that at all affect the operation of the reporting? In Services-Unbound-Logging I see all the logs clearly. In Reporting-Unbound DNS I have nothing on Overview nor anything in the Details tab. I've enabled/disabled it and cleared the stats for it but no change over several hours.

Not a huge deal- just would prefer to have some nicer tools to look at what is going on vs. parsing through logs on Loki.

Edit- along with this, I get weird errors every few weeks it seems that generate crash reports. At first I thought it was something AMD related but maybe not. I debated trying opnsense-bootstrap which, to my understanding, wipes out all the opnsense stuff and reinstalls it from scratch (while somehow not wiping the config?) So I could run that, reboot, and it reinstalls all my plugins and keeps my config? I'm not above doing that or reinstalling if necessary but have never done so and have a lot of config done (multiple VLANs, multiple WG tunnels, policy tagging, etc. etc. that I absolutely do not want to set back up in case of issues.)
Title: Re: Unbound reporting not working on 25.7.10
Post by: wallaby501 on January 22, 2026, 12:12:56 AM
Oddly enough, after another weird reboot (probably need to reinstall) it seems to be working somehow. Maybe it needed time (I gave it a day and no change but I guess it's been a few days at least by now) or something happened with that latest reboot.