Can't access sub-paths in reverse-proxy

[francislavoie]

@Raikatzu

1. Caddy version (caddy version):

2.0.0-alpine

Please upgrade to Caddy v2.3.0, you’re using a version of Caddy that’s more than a year old at this point!

@Raikatzu

    basicauth / {
        XXX XXX
    }

This will only apply authentication to exactly /, i.e. the root of your site and nothing else. Remove the / to apply it to everything.

@Raikatzu

    reverse_proxy /grafana/* {
        to grafana:3000
    }

You can use the shorter syntax:

reverse_proxy /grafana/* grafana:3000

@Raikatzu

    route /influxdb/* {
        uri strip_prefix /influxdb
        reverse_proxy influxdb:8086
    }

After upgrading to v2.3.0, you can use handle_path which shortens this:

    handle_path /influxdb/* {
        reverse_proxy influxdb:8086
    }

---

As for your problem proxying certain services, you’re running into this problem; many apps weren’t designed to run in subpaths, and unless they expose configuration to make it work, never will. The solution is to use subdomains for those services, or in your case use a different port to proxy them with Caddy.

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…