Container fails to start after enableing remote control

[gunnahafta]

Trying to enable remote control in unbound.conf

From:

remote-control:
control-enable: no

To:

remote-control:
control-enable: yes

Upon restart of the container it wont fully start and throws the following errors:

[1707619987] unbound[1:0] error: can't bind socket: Cannot assign requested address for ::1 port 8953
[1707619987] unbound[1:0] error: cannot open control interface ::1 8953
[1707619987] unbound[1:0] fatal error: could not open ports

IP appears to be IPv6. Don't use IPv6 on this network or on the docker host. Not sure why this would only occur when enabling remote control. No sure how these are related.

[MatthewVance]

You also need to make some other changes like providing the crypto keys. See #77 and https://unbound.docs.nlnetlabs.nl/en/latest/getting-started/configuration.html#set-up-remote-control.

[gunnahafta]

By bad forgot to mention I did do those steps also.  Suppose I could have screwed it up I’m not exactly an expert in docker but it seemed straightforward enough looking at the instructions.I’ll double check this and come back.Sent from my iPhoneOn 13 Feb 2024, at 4:26 am, Matthew Vance ***@***.***> wrote: You also need to make some other changes like providing the crypto keys. See #77 and https://unbound.docs.nlnetlabs.nl/en/latest/getting-started/configuration.html#set-up-remote-control. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>