Caddy as reverse proxy for docker services

[francislavoie]

@kpinarci

reverse_proxy 127.0.0.1:3000

When in Docker, 127.0.0.1 (a.k.a. localhost) refers to this container, so Caddy is trying to connect to something within the same container. Which won’t work.

You should use the container name of the other containers to connect to them.

Also, I strongly recommend using subdomains for each service, instead of using subpaths:

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…