Upgrade to v0.108.0-b.67 failed

[rphillips]

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

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.108.0-b.67

Action

I upgraded to v0.108.0-b.67 using the automated button within the website. Usually this works fine, but with this release the AdguardHome binary is failing to start.

root@adguard:/opt/AdGuardHome# ./AdGuardHome
2025/04/17 19:19:48.692167 [info] AdGuard Home, version v0.108.0-b.67
2025/04/17 19:19:48.695718 [info] tls_manager: using default ciphers
2025/04/17 19:19:48.700403 [info] Initializing auth module: /opt/AdGuardHome/data/sessions.db
2025/04/17 19:19:48.700538 [info] auth: initialized.  users:1  sessions:3
2025/04/17 19:19:48.700749 [info] webapi: initializing
2025/04/17 19:19:48.722541 [error] closing query log: flushing log buffer: nothing to write to a file
2025/04/17 19:19:48.722613 [fatal] newServerConfig: constructing tls config: parsing tls key pair: tls: failed to find any PEM data in certificate input

root@adguard:/opt/AdGuardHome# ./AdGuardHome --version
AdGuard Home, version v0.108.0-b.67

Partial Config:

tls:
  enabled: true
  server_name: <redacted>
  force_https: false
  port_https: 55355
  port_dns_over_tls: 785
  port_dns_over_quic: 784
  port_dnscrypt: 0
  dnscrypt_config_file: ""
  allow_unencrypted_doh: true
  certificate_chain: ""
  private_key: ""
  certificate_path: ""
  private_key_path: ""
  strict_sni_check: false

Expected result

Upgrades should be backwards compatible.

Actual result

AdguardHome binary is erroring out upon start.

Additional information and/or screenshots

No response

[rphillips]

Downgrading to v0.108.0-b.66 does work. The AdguardHome binary successfully starts up.

[ainar-g]

@rphillips, just to be clear, do you actually have neither certificate data nor certificate path in the TLS config? Are you using that enabled: true for allow_unencrypted_doh: true?

[ainar-g]

@schzhn, please investigate. It might be that the new validation is too strict and doesn't allow users to enable unencrypted DoH without adding certificates, which is a common configuration for AGH instances behind proxies.

[rphillips]

@ainar-g Yes, correct. I have a reverse proxy (caddy) proxying to the Adguard backend for DOH. There are not any Adguard certificates or keys setup.

[EugeneOne1]

@rphillips, hello. We've just released the beta release that should handle the certificates absence correctly. Could you please confirm if this fixes the issue?

[rphillips]

v0.108.0-b.68 does fix the issue. Thank you!