How to get The reverse_proxy directive to strip the path of the request before forwarding the request upstream

[francislavoie]

@sflamm

reverse_proxy 127.0.0.1:10002 {

Make sure your { match all the closing }. You have an extra one now at the end of the reverse_proxy line.

@sflamm

Now it no longer has a 404… but the page is blank… looking at the page source it looks like it has never loaded the scripts:

That’s not a problem with Caddy. You need to configure your upstream app to be aware of the subpath you’re proxying to, since it constructs the HTML which contain the script tags.

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…

@sflamm

what is the difference? nothing has changed on the application end…

Using handle_path, Caddy will only handle requests which have /version1* in the path. Other requests will go unhandled, which results in an empty 200 response. You either need to configure Caddy to handle those other requests with another handle block, or configure your upstream app to avoid needing to do the handle_path in Caddy.