manup85
Regular Contributor
I used to have similar issues, but haven't experienced since the upgrade to v103.3 of AdGuardHome.
Also I don't know if every time the CPU usage / temperature would go up. Usually if I noticed DNS failures, then I quickly disabled and enabled AdGuardHome again.
Also think the issue happened only (but is has been some while, so don't remember for sure) when using AdGuardHome with its default settings, i.e. when using remote (Quad9 ?? ) upstream dns-servers.
I now use it with pointing AdGuardHome to 192.168.1.1 (i.e. doing the resolving via local dnsmasq instance) and thus not having the DoH/DoT encryptedDNS, but only adblocking.
During such issues, AdGuardHome log would usually show lines like these:
Code:SafeBrowsing: failed: couldn't initialize HTTP client or transport, cause: couldn't do a POST request to 'https://dns-family.adguard.com:443/dns-query', cause: Get "https://dns-family.adguard.com:443/dns-query?dns=olEBAAABAAAAAAAACGlwdjRvbmx5BGFycGEAAAEAAQ": context deadline exceeded 2020/06/17 21:20:45 [info] SafeBrowsing: failed: couldn't initialize HTTP client or transport, cause: timeout exceeded: 17626 ms 2020/06/17 21:20:45 [info] SafeBrowsing: failed: couldn't initialize HTTP client or transport, cause: timeout exceeded: 17627 ms 2020/06/17 21:20:45 [info] SafeBrowsing: failed: couldn't initialize HTTP client or transport, cause: timeout exceeded: 17629 ms 2020/06/17 21:20:46 [info] SafeBrowsing: failed: couldn't initialize HTTP client or transport, cause: timeout exceeded: 11796 ms
i think the issue in exactly how you explained. however after wipe kamoj config + adguard config and reflash b26 i didn't notice any other issues. i would wait to new Voxel release before doing the same with router settings so to start with fresh configuration. i'm still doing some tests and in case.. i'll keep here posted. appreciated