Open trilin6 opened 1 year ago
Hey, everything looks fine in logs and your config. This is probably an issue with your docker setup or your DNS setup for the domain you're using.
Is whoami.pi.local
properly resolving to docker host IP?
whoami.pi.local
should not use .local
as that is reserved for mDNS.
Try with .localhost
.
.local
shouldn't resolve by default, so if you have that configured somewhere else it might be contributing to the issue. Especially if you've got a custom DNS client / router config that has DNS rebind protection enabled IIRC, which can flag private range IPs returned as a security risk.
Try keep it simple first. .localhost
should resolve like localhost
automatically for you in the browser.
Have been having trouble getting caddy-docker-proxy to work on local network. Have a larger docker-compose.yml with quite a few services running, but created a basic whoami to try diagnose the issue.
Whatever I try, the result in browser is either
DNS_PROBE_POSSIBLE
orREFUSED TO CONNECT
Here's my whoami docker-compose.yml:
whoami logs >
caddy logs >