% sudo ./AdGuardHome2024/08/01 23:44:03.973473 [info] AdGuard Home, version v0.107.452024/08/01 23:44:03.977454 [info] tls: using default ciphers2024/08/01 23:44:03.978383 [info] safesearch default: disabled2024/08/01 23:44:03.981912 [info] Initializing auth module: /usr/local/AdGuardHome/data/sessions.db2024/08/01 23:44:03.981975 [info] auth: initialized. users:1 sessions:02024/08/01 23:44:03.982085 [info] tls: number of certs: 22024/08/01 23:44:03.982098 [info] tls: got an intermediate cert2024/08/01 23:44:04.004956 [info] web: initializing2024/08/01 23:44:04.005215 [fatal] filtering: filtering: unknown blocked-service "yy"
% sudo nano /usr/local/AdGuardHome/AdGuardHome.yaml
OP here.Here we go again: One reboot later, Adguard fails to start (and thus does CrowdSec). I can't seem to find proper logs, but trying to start Adguard manually (via sudo) throws the following "fatal" error:Code: [Select]% sudo ./AdGuardHome2024/08/01 23:44:03.973473 [info] AdGuard Home, version v0.107.452024/08/01 23:44:03.977454 [info] tls: using default ciphers2024/08/01 23:44:03.978383 [info] safesearch default: disabled2024/08/01 23:44:03.981912 [info] Initializing auth module: /usr/local/AdGuardHome/data/sessions.db2024/08/01 23:44:03.981975 [info] auth: initialized. users:1 sessions:02024/08/01 23:44:03.982085 [info] tls: number of certs: 22024/08/01 23:44:03.982098 [info] tls: got an intermediate cert2024/08/01 23:44:04.004956 [info] web: initializing2024/08/01 23:44:04.005215 [fatal] filtering: filtering: unknown blocked-service "yy"Also, the "opnsense-revert" patch to bring back the telemetry widget did not survice the reboot. (!)Looks very much like a repeat of this 2023 problem: https://forum.opnsense.org/index.php?topic=35251.0Yep.SOLUTION: edit your AdGuardHome.yaml and remove the offensive service - in my case "yy", see above.Location: /usr/local/AdGuardHome/AdGuardHome.yamlCode: [Select]% sudo nano /usr/local/AdGuardHome/AdGuardHome.yaml
/usr/local/AdGuardHome/AdGuardHome.yaml