Reverse proxy to almost all of my servers does not work (various problems)

[Whitestrake (Matthew Fay)]

Hey all,

Check out my reply in the other thread:

Adding Subdirectories

Hi @James_Hewitt, @vincentp; I run a usenet stack in a homelab, this is one of the most common things people run into when setting these up. The issue is a simple one: Caddy is configured to proxy traffic to Radarr only if the URI begins with /radarr. However, Radarr itself believes it’s being served out of the web root, i.e. /. So, when it directs the client to load /main.js, /theme.css, etc, Caddy sends the request to the wrong upstream server. Two possible fixes: Set the URL base of Rada…

In short, it has to do with the fact that your upstream servers are expecting to serve content from the web root, /, but Caddy is not configured to direct requests for the web root to the correct upstream server. You’ll find that assets such as CSS, JS, and images don’t work, and links and redirects may be broken.

The fix is to configure the upstream server to expect the subfolder (commonly referred to as a URL base), or to give unruly upstream servers their own subdomain so they can make use of the web root.