Unbound fails to start on boot

[lox]

I have two instances installed and running the latest release.

Whenever it reboots unbound won't start.

"The command '/usr/local/sbin/unbound -c '/var/unbound/unbound.conf'' returned exit code '1', the output was '[1560960202] unbound[50455:0] error: can't bind socket: Can't assign requested address for fe80::5868:342b:b04d:bb1f port 53"

But "Register IPv6 link-local addresses" is disables as IPV6 in interfaces configuration is.

If I start it manually after reboot, it starts up properly.

I want to enable monit to monitor it and start it automatically when it fails, but I cannot find the shell command to start/stop it.

[lox]

Bump

[lox]

Bump

[Pocket_Sevens]

I've noticed this too.  After an overnight shutdown (due to storms in the area), I started up my router and found Unbound didn't start.  I was able to manually start Unbound so we could get connectivity.  Is there any reason why it doesn't auto-start upon boot?

[LouieLouie]

Here's the command:

/usr/local/sbin/pluginctl -s unbound start

you can change the 'start' to stop or restart.

I'm attaching a screenshot of my Monit config for Unbound.

[franco]

Is fe80::5868:342b:b04d:bb1f on a PPPoE?


Cheers,
Franco

[circlenaut]

I'm also getting this issue. Put a bandaid on it as suggested with monit. When I search for the ip6 address I see it listed as link#11 and link#12 with Flags "UHS" and Use "0" under System:Routes:Status.

Anyway to figure out what this address is?

[MarcelW]

I have the same issue with these IPv6 bindings.
I dont use any IPv6 on my opnsense but unbound always tries to bind on a IPv6 address.

Code Select Expand

opnsense: /usr/local/etc/rc.bootup: The command '/usr/local/sbin/unbound -c '/var/unbound/unbound.conf'' returned exit code '1', the output was '[1571684608] unbound[58561:0] error: can't bind socket: Can't assign requested address for fe80::d468:38e9:5205:560a port 53 [1571684608] unbound[58561:0] fatal error: could not open ports'

Any ideas?

[mimugmail]

Do you have an OpenVPN instance running?

[u89]

I have this problem too, and YES I have openvpn server running.

[mimugmail]

Can you try to only let it listen on LAN interface?

[u89]

I do confirm. When openvpn server is set up for a single interface only, unbound starts on boot without issues.

[mdbraber]

I've got a similar issue with unbound not restarting and also running an OpenVPN server (where Unbound is set to listen to the LAN + OpenVPN interface). Were you able to solve this?

[bvwj]

Exact same issue listening to LAN and VPN.  I can start it from the GUI, but it would sure be nice if it could start itself.

[verasense]

Is there a solution for this?

When I reboot OpnSense, at some point all my devices are left with apparently no Internet access and it is just a DNS issue - because the Unbound DNS service is stopped.