Apache

Reverse proxy configuration for Radarr is as simple as most other applications. If you've set url_base to something like /radarr, you'll need to include it here of course as well.

  <Location /radarr>
    ProxyPass http://10.0.1.2:7878
    ProxyPassReverse http://10.0.1.2:7878
  </Location>

Nginx

Reverse proxy configuration for Radarr is done like most other applications. Below is a minimal example, in a standard Nginx install this file should be places in /etc/nginx/sites-available and then symlinked to /etc/nginx/sites-enabled.

    server
    {
        listen      80;
        server_name YOUR_DOMAIN;
    
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect off;
        proxy_set_header Host $host;
    
        location /YOUR_URL_BASE
        {
            proxy_pass  http://localhost:7878;
        }
    }

Here YOUR_DOMAIN needs to be replaced with the domain you are using to reverse proxy e.g. radarr.example.com or example.com. If you want nginx to proxy all requests to sonarr, leave out the server_name line and change the listen line to listen 80 default_server.

Similarly YOUR_URL_BASE needs to be replaced with the URL Base set in radarr's settings. If it is empty, the line should read location /.

After reloading nginx you should now be able to find radarr at http://YOUR_DOMAIN/YOUR_URL_BASE.

Caddy

Configuring the reverse proxy for Caddy is really straight forward. The example below is the configuration for Radarr running in a Docker container and proxies the Docker host network:

domain.com {
  proxy / 172.17.0.1:7878 {
    transparent
    websocket
  }
  log stdout
  errors stderr
}

Radarr Config

To ensure your content remains showing, you need to update your config.xml

For example if you choose /radarr as your url base, you'll need to update your config as such:

<Config>
  <LogLevel>Info</LogLevel>
  <Port>7878</Port>
  <UrlBase>/radarr</UrlBase>
...
</Config>