Colamann

Ok, I think I was just being dumb. I had this in my Caddyfile, based on the examples given: reverse_proxy host-ip:8096 I assumed host-ip was a variable that contained the IP of the docker host. I guess it just means "put your host IP here", right? Because doing that worked 🤦‍♂️ Thanks anyway!

Hello, I hope this is the right thread for this question. Thanks in advance for any help. I'm trying to use binhex-caddy-duckdns as a reverse proxy for another docker container listening on port 8096. I left all settings on default, other than adding my duckdns token. My DuckDNS domain is correctly resolved to my public IP, my router correctly forwards the port to my server, and my request is processed by Caddy, but then something goes wrong. In the docker logs I find the error message: dial tcp: lookup host-ip on <MY ROUTER'S IP>:53: no such host Anonymized Caddyfile and full error log message attached. errormsg.txtCaddyfile