Caddy reverse_proxy behind caddy reverse_proxy?

[francislavoie]

@dadatuputi

image: caddy/caddy:alpine

Don’t use caddy/caddy. Use caddy instead. The caddy/caddy image is our CI target, and it should not be used outside of our internal use.

@dadatuputi

handle /nzbget/ {

Path matching is exact in Caddy. That will only handle exactly /nzbget/ and nothing else. You should use /nzbget/* instead.

@dadatuputi

This second reverse_proxy will ideally act as a reverse proxy for several docker services as subdirectories of dl.l.bradford.la.

I’d recommend using subdomains instead of subpaths. See this article:

The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?"

Have you ever tried to reverse proxy an app into its own little subfolder of your domain name? Makes things neat, doesn’t it? Using example.com/foo/ for one app, example.com/bar/ for another. If you’re coming here from one of the selfhosted communities, you might be thinking along the lines of example.com/sonarr/, example.com/radarr/ etc. Chances are, you’ve tried some configuration along these lines: example.com { redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy localhost…

@dadatuputi

"msg": "remote error: tls: internal error",

Turn on the debug global option on both servers, to see more detailed logs.

@dadatuputi

reverse_proxy https://172.16.1.50:443

I think what’s happening is SNI gets set to 172.16.1.50 instead of dl.l.bradford.la which means the upstream doesn’t know the correct certificate to choose.

Why are you proxying over HTTPS? If this is in your local network, then there’s probably no problem with proxying over HTTP instead. The only concern is if there’s untrusted devices in your network that could intercept the traffic. But that’s probably unlikely.