Unbound: problems with encrypted unbound-contol with luci
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
unbound 1.15.0-1
Maintainer: @EricLuehrsen
Environment: OpenWrt SNAPSHOT r18322-942facd14f / LuCI Master git-21.343.55550-008bd89 mips24k
Description:
Problem with setting "Unbound Control App" (LUCI)
When i trying to turn on any encryption (localhost encryption, subnet encryption, subnet static encyption)
unbound process not starting with error in (system) log:
"/var/lib/unbound/etc/unbound/unbound_control.pem: No such file or directory"
same time i can see file "/var/lib/unbound/unbound_control.pem"
and "/etc/unbound/unbound_control.pem", but not "/var/lib/unbound/etc/unbound/unbound_control.pem"
so its looks like some problem with path to unbound chroot somewere in unbound.sh
At all, i have no need to encrypt unbund conrol, "subnet unencrypted" is enougth for small lan
As solution a can use manual config as advised here, but why...
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 with the unbound.sh path-handling mentioned in the report and compare the configured chroot path with the locations of unbound_control.pem. Reproduce the failure by enabling an encrypted Unbound Control option in LuCI and inspect the system log. Done means the encrypted configuration starts successfully and resolves the PEM file from the correct chroot location.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100