Hello! I have 2 services that are only being accessed locally but require HTTPS so I am using Caddy & DuckDNS w/ DNS-01 to reverse proxy them. In DuckDNS, both subdomains are pointing at the local IP address of Caddy, and my Caddyfile has:
service1.duckdns.org:443 { tls { dns duckdns { api_token API-TOKEN } } reverse_proxy 192.168.0.51:8080 } service2.duckdns.org:443 { tls { dns duckdns { api_token API-TOKEN } } reverse_proxy 192.168.0.20:8080 }
The issue is that I can access service1.duckdns.org (within my home network), but I can’t access service2.duckdns.org (502 Bad Gateway). Caddy is running in a LXC in Proxmox, and Service1 is on a different VM on the same Proxmox machine, while Service2 is on a different server on my network. I don’t see any entries in my router’s firewall logs or PiHole that indicates something is blocking it. I enabled logging in Caddy for both services and I am only able to see activity for Service1, so I guess that means something is blocking Service2 from reaching Caddy entirely?
I’m able to access service2 directly from the IP address but I’m a novice in networking so I’m trying to understand and learn what could be causing this. Any help would be appreciated!
hendrik@palaver.p3x.de 12 hours ago
I’d say there’s likely something wrong with your service. Maybe it refuses serving on a domain it’s not configured for? Or there’s something wrong with the headers or something like that. Or the internal network. Anyway, the 502 error is sent by the Caddy server. That means everything from your browser to the Caddy server should be fine. You can reach it. There’s something wrong with the service or the parts in-between the reverse proxy and the application.