Help with configuring Caddy to work with arr apps

https://slrpnk.net/post/24267330

Help with configuring Caddy to work with arr apps - SLRPNK

Hi i can’t get my caddy revers proxy to fuction with the arr apps i eithr get a blank page or with the config i have now i get: ::: spoiler this page The page isn’t redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. This problem can sometimes be caused by disabling or refusing to accept cookies. ::: ::: spoiler Caddyfile config { email [email protected] } domain.com { # qBittorrent redir /qbit /qbit/ handle_path /qbit/* { reverse_proxy 1.1.1.1:8080 { header_up Host {host} header_up X-Real-IP {remote_host} header_up X-Forwarded-For {remote_host} header_up X-Forwarded-Proto {scheme} } } # Sonarr redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy 1.1.1.1:8989 { header_up Host {host} header_up X-Real-IP {remote_host} header_up X-Forwarded-For {remote_host} header_up X-Forwarded-Proto {scheme} } } # Radarr redir /radarr /radarr/ handle_path /radarr/* { reverse_proxy 1.1.1.1:7878 { header_up Host {host} header_up X-Real-IP {remote_host} header_up X-Forwarded-For {remote_host} header_up X-Forwarded-Proto {scheme} } } # Prowlarr redir /prowlarr /prowlarr/ handle_path /prowlarr/* { reverse_proxy 1.1.1.1:9696 { header_up Host {host} header_up X-Real-IP {remote_host} header_up X-Forwarded-For {remote_host} header_up X-Forwarded-Proto {scheme} } } } ::: I’ve tried setting the URL base to /the_name_of_the_arr_app, but it didn’t work. I’ve attempted it with and without the redir /the_name_of_the_arr_app /the_name_of_the_arr_app/. I’m stuck and unsure of how to resolve the issue. It works fine with qBittorrent.

Are all the *arr services aware that they are expected to have a certain basepath?
Yes

Does it make a difference, if that setting uses a trailing slash? Might be it redirects you to the path without, which triggers caddy to redirect you again, and so on and so forth.

You could also, instead of redirecting, rewrite it. Then it is handled serverside without sending the client somewhere else.

I can’t set a trailing slash Radarr removes it. I am not quite sure what you mean, but I have tried rewriting it.

like this, and then visit, but it makes no difference

redir /radarr/ /radarr handle_path /radarr* { reverse_proxy 1.1.1.1:7878 { header_up Host {host} header_up X-Real-IP {remote_host} header_up X-Forwarded-For {remote_host} header_up X-Forwarded-Proto {scheme} } }

You could also, instead of redirecting, rewrite it. Then it is handled serverside without sending the client somewhere else. I am not quite sure what you mean

Is there a reason you’re trying to expose them to the internet? IMO you’re better off not doing that and using Overseer as the only exposed service that talks to everything else. Exposing the whole arr stack is just unwise and unnecessary.
I am using a VPS for it. So I can’t easily access it locally. I thought it might be insecure, but all the seedbox providers do it.

If you use Cloudflare for DNS there is Zero Trust to protect your services.

It’s also possible to run a cloudflared container next to your arrs to tunnel traffic to ports on your other containers rather than needing a reverse proxy. But that’s more appropriate for something on your local network rather than a VPS.

Why are you proxying to your VPS external IP? Caddy listens to your external IP and your arr apps listen to ideally localhost, you should be reverse proxying to localhost.