Replies: 2 comments 2 replies
-
With
Currently I'm not sure what the root cause can be. On a test server I've only started Traefik and AdGuard and removed everything releated to IPv6 what I have added recently to my environment. When I started Traefik the fist time I got following error.
So I've installed
|
Beta Was this translation helpful? Give feedback.
-
Even when it's almost a year later, I face the exact same problem. I can open the AdGuard-Home Dashboard, but I cannot access the DNS over HTTPS server. My tls-settings are the exact same. There is just a problem with the tls-termination. Some thing regarding Traefik and AdGuard-Home. When I use So I would be very open for any help and suggestions! I don't want to change my reverse Proxy just because AGH is not able to read the requests from Traefik or to terminate / start tls properly. And since I don't think it would be much useful for me, to use local certificates just for the communication between Traefik and a service likt AGH, since both the reverse proxy and AdGuard-Home are on the same host on Docker. This would complicate things quite too much for this usecase. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I'm figuring same issues as #4656 - just with using Traefik as proxy.
Current status: DNS and DNS-over-TLS are working well.
Issue to be solved: How do I configure Traefik (and AdGuard), so that DNS-over-HTTPS does also work?
My
AdGuardHome.yaml
looksMy
docker-compose.yml
looksI've tried several things. E.g. adding following
- traefik.http.middlewares.https_redirect.redirectscheme.permanent=true
But all I get is
Client sent an HTTP request to an HTTPS server.
orInternal Server Error
with following label- "traefik.http.services.adguard-doh-svc.loadbalancer.server.scheme=https"
Beta Was this translation helpful? Give feedback.
All reactions