-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNSCrypt response is invalid and cannot be decrypted #6897
Comments
Hi @renatoyamane, thanks for the report. Could you please get me the verbose-level logs with the issue reproduced so we might be able to see better what's happening here? |
Hi @jslawler-gh, Please see the log attached (dnscrypt_log.txt) You can see the error at the line:
|
Same problem v0.107.48 |
How can I remove this tag "waiting for data", as I already submited it? |
seeing the same message here. I only have the Adguard Public DNS sdns as my sole upstream in AGH. Querying
While I can query the sdns upstream myself without issue:
AGH verbose log output:
|
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
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
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
0.107.48
Action
I'm noticing a lot of these errors on my log:
Upstream servers (load balancing mode):
The 3rd (from bottom to top) is an ADGuard DNSCrypt server, which is also resulting in an error reported above.
To reproduce the error quickier, remove the HTTPS, TLS and QUIC servers from the list below.
Bootstrap servers:
Filters:
Same errors also noticed on previous versions (0.107.45 -- 0.107.46 -- 0.107.47)
Expected result
No errors
Actual result
Noticed some errors as reported
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: