Can't access resources which are served as a reverse proxy

[francislavoie]

@marius1553

localhost:8080/dashboard → Show login page

You configured your matcher as /dashboard/*, but made a request like /dashboard, which doesn’t match. You’d need to use /dashboard* to match that request.

Request matchers (Caddyfile) - Caddy Documentation

Also, the handle directive doesn’t manipulate the URL path at all, so requests to your backend will still have /dashboard in it. Is that what you intended? If not, you can use handle_path instead of handle to make it strip the path prefix before proxying.

handle_path (Caddyfile directive) - Caddy Documentation

But keep in mind that if your upstream app wasn’t configured to be aware of the subpath, things can break. Read this article to better understand (so I suggest you use subdomains instead of subpaths if possible):

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…