AdGuard Home does not start after restart

[uroshj]

I've been experiencing an issue for several weeks now with all the latest versions of AdGuard Home. I'm installing it on Proxmox using the following Docker-based script:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/adguard.sh)"
It doesn't seem to matter whether I use the default configuration or set it up manually — the result is the same. AdGuard Home works fine for a few days, including across reboots, but eventually, after one particular reboot, it just stops working entirely.
This setup had been running flawlessly for years, and I haven’t made any changes to my network configuration. I'm trying to understand what might be causing this sudden instability.
Could you help me figure out what’s going wrong?
Also, what troubleshooting steps would you recommend I take to diagnose and resolve this issue?

I currently have 3 instances running.
Installed it yesterday, today again the error:
And today again after reboot.
First one
From file: /var/log/AdGuardHome.err

2025/09/23 11:44:34 [info] service: AdGuard Home, version v0.107.66
2025/09/23 11:44:34 [info] service: control action=run
2025/09/23 11:44:34.114181 [info] AdGuard Home, version v0.107.66
2025/09/23 11:44:34.114190 [info] AdGuard Home is running as a service
2025/09/23 11:44:34.122834 [info] tls_manager: using default ciphers
2025/09/23 11:44:34.133189 [info] webapi: initializing
2025/09/23 11:44:34.133430 [fatal] filtering: filtering: unknown blocked-service ""
025/09/22 15:03:31.651541 [info] dnsproxy: cache enabled size=4096
2025/09/22 15:03:31.651552 [info] dnsproxy: max goroutines is set count=300
2025/09/22 15:03:31.651590 [info] dnsproxy: ratelimit is enabled rps=20 ipv4_subnet_mask_len=24 ipv6_subnet_mask_len=56
2025/09/22 15:03:31.651596 [info] dnsproxy: server will refuse requests of type any
2025/09/22 15:03:31.651601 [info] dnsproxy: upstream mode is set mode=load_balance
2025/09/22 15:03:31.651605 [info] dnsproxy: cache enabled size=4194304
2025/09/22 15:03:31.651610 [info] dnsproxy: max goroutines is set count=300
2025/09/22 15:03:31.652561 [info] permcheck: warning: found unexpected permissions type=directory path=/opt/AdGuardHome perm=0777 want=0700
2025/09/22 15:03:31.652620 [info] webapi: AdGuard Home is available at the following addresses:
2025/09/22 15:03:31.652628 [info] go to http://10.10.10.33:80
2025/09/22 15:03:31.652654 [info] service: starting plain server server=plain addr=10.10.10.33:80
2025/09/22 15:03:31.652861 [info] addrproc: processing addresses
2025/09/22 15:03:32.460009 [info] dnsproxy: starting dns proxy server
2025/09/22 15:03:32.460039 [info] dnsproxy: creating udp server socket addr=10.10.10.33:53
2025/09/22 15:03:32.460110 [info] dnsproxy: listening to udp addr=10.10.10.33:53
2025/09/22 15:03:32.460118 [info] dnsproxy: creating tcp server socket addr=10.10.10.33:53
2025/09/22 15:03:32.460165 [info] dnsproxy: listening to tcp addr=10.10.10.33:53
2025/09/22 15:03:32.469875 [info] dnsproxy: entering udp listener loop addr=10.10.10.33:53
2025/09/22 15:03:32.470045 [info] dnsproxy: entering listener loop proto=tcp addr=10.10.10.33:53
2025/09/22 15:23:45.388968 [error] dnsproxy: response received upstream_type=main addr=https://dns10.quad9.net:443/dns-query proto=tcp status="requesting https://dns10.quad9.net:443/dns-query: Get "https:>
2025/09/22 18:03:46.634049 [error] dnsproxy: response received upstream_type=main addr=https://dns10.quad9.net:443/dns-query proto=tcp status="requesting https://dns10.quad9.net:443/dns-query: Get "https:>
2025/09/22 18:45:40.661863 [error] filtering: unknown service name name=""
2025/09/22 18:46:12.306484 [error] filtering: unknown service name name=""
2025/09/22 18:46:35.232726 [error] filtering: unknown service name name=""
2025/09/22 18:47:13.369608 [error] filtering: unknown service name name=""
2025/09/22 18:48:13.474103 [error] filtering: unknown service name name=""
2025/09/22 18:49:19.944570 [error] filtering: unknown service name name=""
2025/09/22 18:49:41.152245 [error] filtering: unknown service name name=""
2025/09/22 19:02:38.472389 [error] dnsproxy: response received upstream_type=local addr=9.9.9.9:53 proto=udp status="exchanging with 9.9.9.9:53 over udp: read udp 10.10.10.33:57017->9.9.9.9:53: i/o timeout"
2025/09/22 19:02:38.472457 [error] dnsproxy: exchange failed upstream=9.9.9.9:53 question=";54.10.10.10.in-addr.arpa.\tIN\t PTR" duration=2.002263625s err="exchanging with 9.9.9.9:53 over udp: read udp 10.>
2025/09/22 19:03:42.492630 [error] dnsproxy: response received upstream_type=local addr=9.9.9.9:53 proto=udp status="exchanging with 9.9.9.9:53 over udp: read udp 10.10.10.33:59372->9.9.9.9:53: i/o timeout"
2025/09/22 19:03:42.492962 [error] dnsproxy: exchange failed upstream=9.9.9.9:53 question=";121.10.10.10.in-addr.arpa.\tIN\t PTR" duration=2.001855597s err="exchanging with 9.9.9.9:53 over udp: read udp 10>
2025/09/22 19:05:40.966098 [error] dnsproxy: response received upstream_type=local addr=9.9.9.9:53 proto=udp status="exchanging with 9.9.9.9:53 over udp: read udp 10.10.10.33:49460->9.9.9.9:53: i/o timeout"
2025/09/22 19:05:40.966162 [error] dnsproxy: exchange failed upstream=9.9.9.9:53 question=";120.10.10.10.in-addr.arpa.\tIN\t PTR" duration=2.001318228s err="exchanging with 9.9.9.9:53 over udp: read udp 10>
2025/09/22 19:05:44.321981 [error] dnsproxy: response received upstream_type=local addr=9.9.9.9:53 proto=udp status="exchanging with 9.9.9.9:53 over udp: read udp 10.10.10.33:41225->9.9.9.9:53: i/o timeout"
2025/09/22 19:05:44.322044 [error] dnsproxy: exchange failed upstream=9.9.9.9:53 question=";41.10.10.10.in-addr.arpa.\tIN\t PTR" duration=2.000679321s err="exchanging with 9.9.9.9:53 over udp: read udp 10.>
2025/09/22 19:06:23.774203 [error] dnsproxy: response received upstream_type=local addr=9.9.9.9:53 proto=udp status="exchanging with 9.9.9.9:53 over udp: read udp 10.10.10.33:36673->9.9.9.9:53: i/o timeout"
2025/09/22 19:06:23.774267 [error] dnsproxy: exchange failed upstream=9.9.9.9:53 question=";124.10.10.10.in-addr.arpa.\tIN\t PTR" duration=2.002237844s err="exchanging with 9.9.9.9:53 over udp: read udp 10>
2025/09/22 19:16:54.534165 [error] dnsproxy: exchange failed upstream=https://dns10.quad9.net:443/dns-query question=";spclient.wg.spotify.com.\tIN\t A" duration=20.036333255s err="returned: "expected sta>
2025/09/22 19:49:49.647505 [error] dnsproxy: reading msg proto=tcp err="reading len: read tcp 10.10.10.33:53->10.10.10.53:50882: read: connection reset by peer"
2025/09/22 21:10:00.286092 [error] filtering: unknown service name name=""
2025/09/22 21:10:00.334933 [error] filtering: unknown service name name=""
2025/09/22 21:10:35.417865 [error] filtering: unknown service name name=""
2025/09/22 21:10:35.418135 [error] filtering: unknown service name name=""
2025/09/22 21:10:40.648608 [error] filtering: unknown service name name=""
2025/09/22 21:10:40.648863 [error] filtering: unknown service name name=""
2025/09/22 21:10:54.294814 [error] filtering: unknown service name name=""
2025/09/22 21:11:00.411052 [error] filtering: unknown service name name=""
2025/09/22 21:11:34.423915 [error] filtering: unknown service name name=""
2025/09/22 21:11:34.424183 [error] filtering: unknown service name name=""
2025/09/22 21:11:35.256030 [error] filtering: unknown service name name=""
2025/09/22 21:11:39.415452 [error] filtering: unknown service name name=""
2025/09/22 21:12:00.482207 [error] filtering: unknown service name name=""
2025/09/22 21:12:49.562599 [error] filtering: unknown service name name=""
2025/09/22 21:13:34.625601 [error] filtering: unknown service name name=""
2025/09/22 21:13:56.157879 [error] filtering: unknown service name name=""
2025/09/22 21:13:56.158141 [error] filtering: unknown service name name=""
2025/09/22 21:14:29.271358 [error] filtering: unknown service name name=""
2025/09/22 21:14:34.705302 [error] filtering: unknown service name name=""
2025/09/22 21:14:35.409313 [error] filtering: unknown service name name=""
2025/09/22 21:14:35.409547 [error] filtering: unknown service name name=""
2025/09/22 21:14:57.732084 [error] filtering: unknown service name name=""
2025/09/22 21:15:13.747588 [error] filtering: unknown service name name=""
2025/09/22 21:15:27.011081 [error] filtering: unknown service name name=""
2025/09/22 21:15:32.949001 [error] filtering: unknown service name name=""
2025/09/22 21:15:46.818838 [error] filtering: unknown service name name=""
2025/09/22 21:15:54.464688 [error] filtering: unknown service name name=""
2025/09/22 21:16:34.426451 [error] filtering: unknown service name name=""
2025/09/22 21:16:34.426681 [error] filtering: unknown service name name=""
2025/09/22 21:16:35.258989 [error] filtering: unknown service name name=""
2025/09/22 21:16:39.545808 [error] filtering: unknown service name name=""
2025/09/22 21:16:45.463963 [error] filtering: unknown service name name=""
2025/09/22 21:16:46.904275 [error] filtering: unknown service name name=""
2025/09/22 21:17:17.221406 [error] filtering: unknown service name name=""
2025/09/22 21:17:41.287592 [error] filtering: unknown service name name=""
2025/09/22 21:17:46.960189 [error] filtering: unknown service name name=""
2025/09/22 21:18:22.448684 [error] filtering: unknown service name name=""
2025/09/22 21:18:35.457556 [error] filtering: unknown service name name=""
2025/09/22 21:18:35.457799 [error] filtering: unknown service name name=""
2025/09/22 21:18:47.046420 [error] filtering: unknown service name name=""

root@AG-34:/var/log# service AdGuardHome status
● AdGuardHome.service - AdGuard Home: Network-level blocker
Loaded: loaded (/etc/systemd/system/AdGuardHome.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-09-23 11:49:31 CEST; 4s ago
Process: 305 ExecStart=/opt/AdGuardHome/AdGuardHome -s run (code=exited, status=1/FAILURE)
Main PID: 305 (code=exited, status=1/FAILURE)
CPU: 31ms

Second one:
2025/09/23 11:52:05 [info] service: AdGuard Home, version v0.107.66
2025/09/23 11:52:05 [info] service: control action=run
2025/09/23 11:52:05.690657 [info] AdGuard Home, version v0.107.66
2025/09/23 11:52:05.690679 [info] AdGuard Home is running as a service
2025/09/23 11:52:05.701184 [info] tls_manager: using default ciphers
2025/09/23 11:52:05.785183 [info] webapi: initializing
2025/09/23 11:52:05.785436 [fatal] filtering: filtering: unknown blocked-service ""
d; trying to disable private RDNS resolution
2025/09/22 15:02:16.234968 [info] dnsproxy: upstream mode is set mode=load_balance
2025/09/22 15:02:16.234976 [info] dnsproxy: cache enabled size=4096
2025/09/22 15:02:16.234986 [info] dnsproxy: max goroutines is set count=300
2025/09/22 15:02:16.235008 [info] dnsproxy: ratelimit is enabled rps=20 ipv4_subnet_mask_len=24 ipv6_subnet_mask_len=56
2025/09/22 15:02:16.235013 [info] dnsproxy: server will refuse requests of type any
2025/09/22 15:02:16.235017 [info] dnsproxy: upstream mode is set mode=load_balance
2025/09/22 15:02:16.235021 [info] dnsproxy: cache enabled size=4194304
2025/09/22 15:02:16.235025 [info] dnsproxy: max goroutines is set count=300
2025/09/22 15:02:16.235763 [info] permcheck: warning: found unexpected permissions type=directory path=/opt/AdGuardHome perm=0755 want=0700
2025/09/22 15:02:16.235815 [info] webapi: AdGuard Home is available at the following addresses:
2025/09/22 15:02:16.235945 [info] go to http://127.0.0.1:80
2025/09/22 15:02:16.235950 [info] go to http://[::1]:80
2025/09/22 15:02:16.235952 [info] go to http://[fe80::2dcf:1f31:1dc6:305e%eth0]:80
2025/09/22 15:02:16.235978 [info] service: starting plain server server=plain addr=0.0.0.0:80
2025/09/22 15:02:16.236143 [info] addrproc: processing addresses
2025/09/22 15:02:16.811920 [info] dnsproxy: starting dns proxy server
2025/09/22 15:02:16.811948 [info] dnsproxy: creating udp server socket addr=0.0.0.0:53
2025/09/22 15:02:16.812012 [info] dnsproxy: listening to udp addr=[::]:53
2025/09/22 15:02:16.812077 [info] dnsproxy: creating tcp server socket addr=0.0.0.0:53
2025/09/22 15:02:16.812127 [info] dnsproxy: listening to tcp addr=[::]:53
2025/09/22 15:02:16.815556 [info] dnsproxy: entering udp listener loop addr=[::]:53
2025/09/22 15:02:16.815630 [info] dnsproxy: entering listener loop proto=tcp addr=[::]:53
2025/09/22 16:45:41.352277 [error] dnsproxy: response received upstream_type=main addr=https://dns10.quad9.net:443/dns-query proto=tcp status="requesting https://dns10.quad9.net:443/dns-query: Get "https:>
2025/09/22 18:14:58.000954 [error] dnsproxy: exchange failed upstream=https://dns10.quad9.net:443/dns-query question=";e-uprava.gov.si.\tIN\t HTTPS" duration=3.980201077s err="expected status 200, got 502 >
2025/09/22 18:14:58.001055 [error] dnsproxy: handling request proto=tcp err="using request handler: expected status 200, got 502 from https://dns10.quad9.net:443/dns-query"
2025/09/22 18:17:34.335131 [error] dnsproxy: reading msg proto=tcp err="reading len: read tcp 10.10.10.32:53->10.10.10.53:51872: read: connection reset by peer"
2025/09/22 18:27:20.218190 [error] dnsproxy: response received upstream_type=main addr=https://dns10.quad9.net:443/dns-query proto=tcp status="requesting https://dns10.quad9.net:443/dns-query: Get "https:>
2025/09/22 18:45:40.666692 [error] filtering: unknown service name name=""
2025/09/22 18:46:12.309141 [error] filtering: unknown service name name=""
2025/09/22 18:46:35.237445 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257225 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257438 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257653 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257665 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257674 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257686 [error] filtering: unknown service name name=""
2025/09/22 18:46:56.257695 [error] filtering: unknown service name name=""

[schzhn]

The logs indicate there’s an empty ID ("") in the config under filtering.blocked_services.ids (global) or clients.persistent[*].blocked_services.ids (per-client).

Empty IDs are invalid. AdGuard Home validates them at startup and via the new API (/control/blocked_services/update), so it fails with unknown blocked-service "" on restart.

The legacy endpoint (/control/blocked_services/set) didn’t validate and could write "" into the config; using it can corrupt the list and prevent AGH from starting.

[uroshj]

Ay the system does not have an option to block services for example over HomeAssistant (which my wife is able tk use) to add/remlve blocked services, I am doing it over script. There I set "" for none.
At least I now know what the issue is.
Thank you for the great support.
Do you maybe know if there will be some similar options added to the HA addon?
Thank you!

[schzhn]

To disable all blocked services, use the new API:
PUT /control/blocked_services/update with body {"ids":[]}.
Or use the old endpoint, POST /control/blocked_services/set, with payload [].
I don’t have information on the HA add-on’s feature plans.