Open SukkaW opened 3 weeks ago
Same issue, v0.107.53
takes ~20s to resolve through DoH and throws several generic timeout messages. The problem is gone after reverting back to v0.107.52
.
Possibly related: https://github.com/AdguardTeam/AdGuardHome/issues/7346 (similar issue from v0.108.0-b.58, which is released between these two versions).
Environment: Linux 4.1.52 aarch64 ASUSWRT-Merlin 3004.388.7
I'm stunned by the huge amount of changes between these two versions, not sure how to investigate what's going on from these 29,523 additions and 27,647 deletions
.
@xWTF Even w/ verbose logging I can't see any useful information. So I assume the most likely cause would be the bumping of go from 1.22
to 1.23
.
@xWTF Even w/ verbose logging I can't see any useful information. So I assume the most likely cause would be the bumping of go from
1.22
to1.23
.
Yep, on my device the log simply says "timeout" without any additional information, appears to be a regular connection problem but curl and old version works fine. Nothing suspicious from the changelog / milestone, so the version bump could be the cause. Currently I don't have evidence tho, the changes are just too much for me to review.
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
Raspberry Pi 4
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.53
Action
Replace the following command with the one you're calling or a description of the failing action:
Expected result
The result returned immdiately.
Actual result
The result returned in about 20 seconds.
Additional information and/or screenshots
I have set following upstream servers in the
DNS settings
:But when I use the
Test upstreams
button, AdGuardHome says all those servers could not be used:I have tested those servers locally, they return the result very fast, so definitely no internet connectivity issue, and also there is no problem with the upstream servers:
I have also tried with
curl
:I then enabled
log.verbose
in the config file (AdGuardHome.yaml
), and I got those logs:Also average upstream servers response time:
So somehow AdGuardHome failed to connect to upstream servers while
dig
works just fine.