AdGuardHome
AdGuardHome copied to clipboard
Issues with QUIC upstreams
Prerequisites
-
[x] I have checked the Wiki and Discussions and found no answer
-
[x] I have searched other issues and found no duplicates
-
[x] I want to report a bug and not ask a question or ask for help
-
[x] 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, ARM64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.58
Action
QUIC upstream resulting in the following lines in the log:
Mar 30 20:18:06 raspberrypi5 AdGuardHome[27663]: 2025/03/30 20:18:06.766632 [error] dnsproxy: exchange failed upstream=quic://dns.adguard-dns.com:853 question=";www.jbl.com.\tIN\t AAAA" duration=124.223881ms err="reading response from quic://dns.adguard-dns.com:853: Application error 0x0 (local)"
This issue appears in v0.107.58 and v0.107.59. It works fine in v0.107.56
Despite the above log, the resolution works as it can be seen in the query logs, however, there seems to be a lag, indicating that not all queries are being resolved.
Expected result
There should not be any log lines indicating this type of error
Actual result
Errors in the log.
Additional information and/or screenshots
No response
Can you please confirm 100% that rolling back to v0.107.56 doesn't produce this error? If so I'll flag to up to the developers.
Thanks!
Hi,
v0.107.56 is definitely clean. See screenshot 1 - i also ran it overnight without any errors. v0.107.57 might be clean too. could not reproduce the error in the 20 minutes i ran this. see screenshot 2. v0.107.58 - can reproduce immediately upon restarting. See screenshot 3 v0.107.59 - same, can reproduce immediately upon restarting. See screenshot 4.
Hope this helps. let me know if i need to share any more information.
Hello, is there any feedback or update on this? I am holding back on updating. Kindly let me know if you'd like me to provide more logs. Tx
This (same error in syslogs and considerable response lag seen in query log for encrypted queries) is still present in v0.108.0-b.68 and edge as of today (v0.108.0-a.1088+61a1403e), but curiously is only seen for persistent clients which have custom upstreams configured (as in https://github.com/AdguardTeam/AdGuardHome/issues/7769).
Would appreciate a response from the team. I am still on the older version.
I may have a fix for this but it's still unconfirmed. Please give it a try if you'd like: https://github.com/AdguardTeam/AdGuardHome/pull/7789