You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The remote-control feature fails to start due to permission errors accessing the .pem files. The logs show repeated “Permission denied” errors when loading the certificate chain file, causing Unbound to fail initialization.
Dec 17 11:30:26 router unbound[105138]: Dec 17 11:30:26 unbound[105138:0] error: Error in SSL_CTX use_certificate_chain_file crypto error:8000000D:system library::Permission denied
Dec 17 11:30:26 router unbound[105138]: Dec 17 11:30:26 unbound[105138:0] error: and additionally crypto error:10080002:BIO routines::system lib
Dec 17 11:30:26 router unbound[105138]: Dec 17 11:30:26 unbound[105138:0] error: and additionally crypto error:0A080002:SSL routines::system lib
Dec 17 11:30:26 router unbound[105138]: Dec 17 11:30:26 unbound[105138:0] fatal error: could not set up remote-control
Hi there, it seems you are modifying a system configured Unbound (which comes with its own systemctl scripts and apparmor profile). I cannot help you with the apparmor side of things, but turning it off to see if that would solve the permission errors would be my first action.
If you only care about the remote control working, this is enabled by default in the debian system Unbound as you can see in /etc/unbound/unbound.conf.d/remote-control.conf. It communicates over unix domain sockets and the system apparmor profile is tailored to that. (I see that you edited the system apparmor profile btw).
It makes sense to have permissions errors before the modifications because access to those files is explicitly denied in the default configuration AFAICS. I don't have any experience with apparmor to identify the issue but try to disable apparmor for Unbound completely and see if it solves the permission problem. If that is the case, you can then focus on finetuning the profile.
Describe the bug
The remote-control feature fails to start due to permission errors accessing the .pem files. The logs show repeated “Permission denied” errors when loading the certificate chain file, causing Unbound to fail initialization.
Steps to reproduce the behavior:
sudo -u unbound unbound-control-setup
sudo systemctl restart unbound
Expected behavior
Unbound should start successfully and allow remote-control commands without permission errors.
System:
unbound -V
output:Additional information
Permissions
Config
Unit
/etc/apparmor.d/usr.sbin.unbound
The text was updated successfully, but these errors were encountered: