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 Radarr so it knows it’s serving out of the
/radarrsubfolder
(You can set this in Settings → General, under Start Up, and requires a restart of Radarr) - Use a subdomain, rather than a subfolder (e.g.
radarr.example.com).
Of course, the former fix requires you have access to a working Radarr to get to the settings. You can probably just load it from 192.168.x.2:7878 to toggle the setting and get it working.
The former also works on Sonarr, and NZBGet is quite permissive of directory regardless, but for other apps that don’t have a URL base setting (or similar), you’re left with using a subdomain (or trying to use http.filter to edit any links coming back from the proxy).