Problem with latest update

Started by ricostuart, January 20, 2025, 02:43:34 PM

Previous topic - Next topic
I've just updated opnsense to 24.7.12. Now the internet stopped working.
My setup is-
Opnsense running as vm in proxmox
Adguardhome running as plugin in opnsense

opnsense used adguard as primary dns --> unbound as upstream dns --> kea as dhcp in opnsense.

It seems that unbound will not load:

Script action failed with Command '/usr/local/opnsense/scripts/unbound/wrapper.py -s ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 78, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/unbound/wrapper.py -s ' returned non-zero exit status 1.
I changed my adguard settings to bypass unbound to 1.1.1.1 and have it running again.
What has changed with unbound? Is there a way to find out what exactly is going wrong?

So after some searching, it seems a change in kea / unbound has caused it to error out if there are any spaces and / or any underscores. So I went through it all and changed all reservations to have neither of those. This then allowed unbound to startup. Chagned adguard back to the original settings and it seems to be working again.