Replies: 1 comment
-
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.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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