Unbound DNS fails to start after reboot - manual start works

[alex-1987]

Important notices

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

I’m having an issue with Unbound DNS not starting automatically after I reboot OPNsense. The settings are all on default, and the only option I have enabled is "Enable Unbound."

Network interfaces are set to "All."

Previously, everything was working fine, but now I’m seeing the following error message in the logs

However, when I manually start the Unbound service, it works without any problems.

When I run the command configctl unbound check, it gives the following output:

no errors in /var/unbound/unbound.conf

To Reproduce

Steps to reproduce the behavior:

1. Restart OpnSense

Expected behavior

Unbound DNS start

Relevant log files

configd.py [125028be-a76c-4702-8bf1-8bf448b7040d] 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 76, 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.

Environment
Versionen
OPNsense 24.7.6-amd64
FreeBSD 14.1-RELEASE-p5
OpenSSL 3.0.15