Hi, I’m having trouble getting my Caddy reverse proxy to work with the arr apps I can access everything without the reverse proxy. I have set the basic login prompt (like this one) through the arr apps after I logge in to one of the arr apps I either get a blank page or I’m seeing this error page:
firefox
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.
chromium
This page isn’t working domain.com redirected you too many times.
Try deleting your cookies. ERR_TOO_MANY_REDIRECTS
Caddyfile config (1.1.1.1 is a placeholder ip for my vps external ip)
{
email email@domain.com
}
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.
radarr debug log
2025-07-04 21:27:45.9|Info|Radarr.Http.Authentication.BasicAuthenticationHandler|Basic was not authenticated. Failure message: Authorization header missing.
2025-07-04 21:27:45.9|Info|Radarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was challenged.
2025-07-04 21:27:54.1|Debug|Radarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was successfully authenticated.
2025-07-04 21:27:54.8|Debug|Radarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was successfully authenticated.
2025-07-04 21:27:55.0|Debug|Radarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was successfully authenticated.
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 exposed it all because I am on a VPS, i don’t know how to configure it otherwise, and I did not think it was a problem because all the seedboxes expose it all.
I don’t want to run Jellyfin/Plex because I am on a VPS with low resources.
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.