Replies: 2 comments
-
No clue on my side either, but I just faced the same issue, so subscribing to the topic. |
Beta Was this translation helpful? Give feedback.
-
There may be an issue with how you’re testing your DOH server. For reference, I use curl –doh-url and doggo for testing purposes. For those setting up DOH behind a Caddy server, the allow_unencrypted_doh: true option doesn’t seem to work well. If the upstream server is set to use HTTP for transport, ADH will return a 400 error regardless of the client’s request. My working configuration uses HTTPS for the upstream server but disables TLS verification because the internal address of ADH is being used.
|
Beta Was this translation helpful? Give feedback.
-
I had an instance of AdGuardHome behind nginx proxy. Everything worked as expected until I decided to pull new AdGuardHome docker image. After pulling the latest image I restarted docker compose. At this point I lost my current configuration (my bad) and started to configuring fresh installation of AdguardHome.
This time everything worked fine until I started to set up encryption settings. In my configuration, nginx rules https for web, but AdGuardHome rules DoH with exact certificate as nginx, and doh requests proxied through nginx. When I tried to reach /dns-query I got the the message
At the time I thought that It was a mistake with nginx configuration. After some efforts I just turned off the nginx to check "bare" installation. And there I got the same result
HTTP/1.1 400 Bad Request
. I tried browser, curl, wget - same result. Here my latest docker config with error.Here my encryption settings
Any clues?
Beta Was this translation helpful? Give feedback.
All reactions