|
This seems related to Remote Control Options. Is it enabled? If so
disable it and see if the errors disappear. In case you require remote control you may look into the documentation https://www.nlnetlabs.nl/documentation/unbound/unbound.conf/ about control-use-cert: and following. On 23.11.2018 17:44, via Unbound-users
wrote:
I've just started using unbound, which seems to be working well. However, I get these in syslog:systemd[1]: Started Unbound recursive Domain Name Server. unbound[1462]: [1462:0] notice: init module 0: ipsecmod unbound[1462]: [1462:0] notice: init module 1: validator [1462:0] notice: init module 2: iterator [1462:0] info: start of service (unbound 1.7.3). [1462:0] notice: failed connection from 127.0.0.1 port 60088 [1462:0] error: remote control failed ssl crypto error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate [1462:1] info: generate keytag query _ta-4a5c-4f66. NULL IN [1462:0] error: can't bind socket: Permission denied for 0.0.0.0 [1462:0] error: can't bind socket: Permission denied for 0.0.0.0 Anything I need to do ? For instance, what bad certificate, and how do I replace it ? sean |
- warning messages on startup : should I be... Sean Darcy via Unbound-users
- Re: warning messages on startup : sh... ѽ҉ᶬḳ℠ via Unbound-users
- Re: warning messages on startup ... Jaap Akkerhuis via Unbound-users
