Description
Prerequisites
-
I have checked the Wiki and Discussions and found no answer
-
I have searched other issues and found no duplicates
-
I want to report a bug and not ask a question or ask for help
-
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
Docker
Setup
On one machine
AdGuard Home version
V0.107.62
Action
I updated from V0.107.61 to V0.107.62 via docker pull command. Usually, it works perfectly fine but not this time
adguardhome | 2025/05/31 23:02:55.989284 [info] AdGuard Home, version v0.107.62
adguardhome | 2025/05/31 23:02:56.009015 [info] tls_manager: using default ciphers
adguardhome | 2025/05/31 23:02:56.023864 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
adguardhome | 2025/05/31 23:02:56.024232 [info] auth: initialized. users:1 sessions:0
adguardhome | 2025/05/31 23:02:56.024337 [info] webapi: initializing
adguardhome | 2025/05/31 23:02:56.194808 [error] closing query log: flushing log buffer: nothing to write to a file
adguardhome | 2025/05/31 23:02:56.194847 [fatal] newServerConfig: constructing tls config: parsing tls key pair: tls: failed to find any PEM data in certificate input
adguardhome exited with code 0
Below, my tls
section
tls:
enabled: true
server_name: ""
force_https: false
port_https: 443
port_dns_over_tls: 853
port_dns_over_quic: 853
port_dnscrypt: some_value
dnscrypt_config_file: /opt/adguardhome/conf/dnscrypt.yaml
allow_unencrypted_doh: false
certificate_chain: ""
private_key: ""
certificate_path: ""
private_key_path: ""
strict_sni_check: false
I do not use DoH, only DNSCrypt. According to the documentation, there is nothing more to add.
https://github.com/AdguardTeam/Adguardhome/wiki/DNSCrypt
Expected result
V0.107.62 to work like previous working version
Actual result
No errors at start-up
Additional information and/or screenshots
This issue looks very similar to #7773
As a work around, I have set
allow_unencrypted_doh: true
V0.107.62 is now starting correctly. What bother me, I do not use DoH and this setting was not used previously.