unbound-control: Looking for SSL Cert in the wrong directory
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @BKPepe @EricLuehrsen
Environment: (put here arch, model, OpenWrt version) ARMv7, GL.iNet GL-B1300, Version 22.03
Description:
The following packages were installed: luci-app-unbound, unbound-control, unbound-control-setup
During setup I wanted to enable the following in luci:
Services->Recursive DNS->Unbound->Resource
Unbound Control App: Local Host, Encrypted
The certificates are generated in /etc/unbound but unbound-control seems to expect them in /var/lib/unbound/etc/unbound/unbound_control.pem
When trying to query the unbound-conrol status via terminal I will get the following error
root@OpenWrt:~# unbound-control status
error: Error setting up SSL_CTX client cert
/var/lib/unbound/etc/unbound/unbound_control.pem: No such file or directory
Manually creating the expected directory and adding the cert fixes the problem until the devices is restarted. I was unable to find an option to point unbound-control to the correct location.
It would be great if this could be fixed! Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running unbound-control status after installing luci-app-unbound, unbound-control, and unbound-control-setup, then compare /etc/unbound with the expected /var/lib/unbound/etc/unbound/unbound_control.pem path. Trace the package setup and restart behavior; done means the command finds the generated certificate without manual copying and continues to work after reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100