DNSCrypt response is invalid and cannot be decrypted about adguardhome HOT 7 OPEN

Hi @renatoyamane, thanks for the report.
I am unable to reproduce this on my own build.

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?

from adguardhome.

Hi @jslawler-gh,

Please see the log attached (dnscrypt_log.txt)

You can see the error at the line:

Mon Apr 8 18:13:18 2024 user.notice AdGuardHome[27886]: 2024/04/08 17:13:18.275573 27886#2310 [error] dnsproxy: upstream sdns://AQIAAAAAAAAAETk0LjE0MC4xNC4xNDo1NDQzINErR_JS3PLCu_iZEIbq95zkSV2LFsigxDIuUso_OQhzIjIuZG5zY3J5cHQuZGVmYXVsdC5uczEuYWRndWFyZC5jb20 failed to exchange ;nxdomain-75wuuuay5j8.biz. IN A in 9.666776ms: exchanging: dnscrypt: DNSCrypt response is invalid and cannot be decrypted

from adguardhome.

Some problem: Versão: v0.107.48

2024/04/09 11:36:50.586816 [error] dnsproxy: https://dns12.quad9.net:443/dns-query: response received over tcp: "requesting https://dns12.quad9.net:443/dns-query: Get "https://dns12.quad9.net:443/dns-query?dns=AAABAAABAAAAAAABBXdob2lzBGFyaW4DbmV0AAABAAEAACkIAAAAgAAAAA\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

from adguardhome.

Same problem v0.107.48

from adguardhome.

How can I remove this tag "waiting for data", as I already submited it?

from adguardhome.

It's also weird because even with a very short response time, DNSCrypt servers are not selected by Adguard:

from adguardhome.

Can be something related to the timezone?

I'm on Summer Time (GMT +1)

My computer and my router are on the correct time and timezone, but I noticed this:

from adguardhome.