Radarr is supported natively on Windows. Radarr can be installed on Windows as Windows Service or system tray application.
Windows versions are limited for support to those currently supported by Microsoft, others may work but this is an unsupported configuration
A Windows Service runs even when the user is not logged in, but special care must be taken since Windows Services cannot access network drives (X:\ mapped drives or \\server\share UNC paths) without special configuration steps.
Additionally the Windows Service runs under the 'Local Service' account, by default this account does not have permissions to access your user's home directory unless permissions have been assigned manually. This is particularly relevant when using download clients that are configured to download to your home directory.
It's therefore advisable to install Radarr as a system tray application if the user can remain logged in. The option to do so is provided during the installer.
You may have to run once "As Administrator" after installing if you get an access error -- such as Access to the path
C:\ProgramData\Radarr\config.xmlis denied -- or you use mapped network drives. This gives Radarr the permissions it needs. You should not need to run As Administrator every time.
It is possible to install Radarr manually using the x64 .zip download. However in that case you must manually deal with dependencies, installation and permissions.
Radarr is not compatible with OSX versions < 10.15 (Catalina) due to .NET incompatibilities.
codesign --force --deep -s - Radarr.appRadarr uses a bundled version of ffprobe for media file analysis and does not require ffprobe or ffmpeg to be installed on the system. If Radarr says Ffprobe is not found this can typically be fixed with a reinstall.
Note: Raspberry Pi OS and Raspbian are both flavors of Debian
For the Debian / Ubuntu / Raspbian beginners there isn't an Apt Repository or Deb package.
If you want an easy life, follow this community provided and maintained Easy Install script for a base Debian (Raspbian / Raspberry Pi OS) / Ubuntu install.
For the official installation instructions that are 'Hands on' follow the Debian / Ubuntu Hands on Install steps further below.
Please see the *Arr Community Installation Script
Radarr uses a bundled version of ffprobe for media file analysis and does not require ffprobe or ffmpeg to be installed on the system. If Radarr says Ffprobe is not found this can typically be fixed with a reinstall.
You'll need to install the binaries using the below commands.
The steps below will download Radarr and install it into
/opt
Radarr will run under the userradarrand groupmedia;mediais the commonly suggested group to run the *Arrs, download clients, and media server under.
Radarr's configuration files will be stored in/var/lib/radarr
sudo apt install curl sqlite3
Warning: Ignoring the below prerequisites will result in a failed installation and non-functional application.
Installation Prerequisites
The below instructions are based on the following prerequisites. Change the instructions as needed to suit your specific needs if necessary.
* The userradarris created
* The userradarris part of the groupmedia
* Your download clients and media server run as and are a part of the groupmedia
* Your paths used by your download clients and media server are accessible (read/write) to the groupmedia
* You created the directory/var/lib/radarrand ensured the userradarrhas read/write permissions for it for it
By continuing below, you acknowledge that you have read and met the above requirements.
dpkg --print-architecture
arch=x64arch=armarch=arm64wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'
tar -xvzf Radarr*.linux*.tar.gz
/opt/sudo mv Radarr /opt/
Note: This assumes you will run as the user
radarrand groupmedia. You may change this to fit your usecase. It's important to choose these correctly to avoid permission issues with your media files. We suggest you keep at least the group name identical between your download client(s) and Radarr.
sudo chown radarr:radarr -R /opt/Radarr
The below systemd creation script will use a data directory of
/var/lib/radarr. Ensure it exists or modify it as needed. For the default data directory of/home/$USER/.config/Radarrsimply remove the-dataargument. Note: that$USERis the User Radarr runs as and is defined below.
cat << EOF | sudo tee /etc/systemd/system/radarr.service > /dev/null
[Unit]
Description=Radarr Daemon
After=syslog.target network.target
[Service]
User=radarr
Group=media
Type=simple
ExecStart=/opt/Radarr/Radarr -nobrowser -data=/var/lib/radarr/
TimeoutStopSec=20
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl -q daemon-reload
sudo systemctl enable --now -q radarr
rm Radarr*.linux*.tar.gz
Typically to access the Radarr web GUI browse to http://{Your server IP Address}:7878
Radarr uses a bundled version of ffprobe for media file analysis and does not require ffprobe or ffmpeg to be installed on the system. If Radarr says Ffprobe is not found this can typically be fixed with a reinstall.
If Radarr did not appear to start, then check the status of the service:
sudo journalctl --since today -u radarr
To uninstall and purge:
Warning: This will destroy your application data.
sudo systemctl stop radarr
sudo rm -rf /opt/Radarr
sudo rm -rf /var/lib/radarr
sudo rm -rf /etc/systemd/system/radarr.service
sudo systemctl -q daemon-reload
To uninstall and keep your application data:
sudo systemctl stop radarr
sudo rm -rf /opt/Radarr
sudo rm -rf /etc/systemd/system/radarr.service
sudo systemctl -q daemon-reload
The Radarr team only provides builds for FreeBSD. Plugins and Ports are maintained and created by the FreeBSD community.
Instructions for FreeBSD installations are also maintained by the FreeBSD community and anyone with a GitHub account may update the wiki as needed.
From the main screen select Jails
Click ADD
Click Advanced Jail Creation
Name (any name will work): Radarr
Jail Type: Default (Clone Jail)
Release: 12.2-Release (or newer)
Configure Basic Properties to your liking
Configure Jail Properties to your liking but add
allow_raw_socketsis helpful for troubleshooting (e.g. ping, traceroute) but is not a requirement.
Configure Network Properties to your liking
Configure Custom Properties to your liking
Click Save
After the jail is created it will start automatically. One more property is required to be set in order for Radarr to see the storage space of your mounted media locations. Open a root shell on the server and enter these commands:
iocage stop <jailname>
iocage set enforce_statfs=1 <jailname>
iocage start <jailname>
Back on the jails list find your newly created jail for radarr and click Shell
To install Radarr
* Ensure your pkg repo is configured to get packages from
/latestand not/quarterly
* Check/usr/local/etc/pkg/repos/FreeBSD.conf
* If that does not exist, copy over/etc/pkg/FreeBSD.confto that location, open it, and replacequarterlywithlatest
pkg install radarr
Don't close the shell out yet we still have a few more things!
Now that we have it installed a few more steps are required.
Time to enable the service but before we do, a note:
The updater is disabled by default. The pkg-message gives instructions on how to enable the updater but keep in mind: this can break things like pkg check -s and pkg remove for Radarr when the built-in updater replaces files.
To enable the service:
sysrc radarr_enable=TRUE
If you do not want to use user/group radarr you will need to tell the service file what user/group it should be running under
sysrc radarr_user="USER_YOU_WANT"
sysrc radarr_group="GROUP_YOU_WANT"
radarr stores its data, config, logs, and PID files in /usr/local/radarr by default. The service file will create this and take ownership of it IF AND ONLY IF IT DOES NOT EXIST. If you want to store these files in a different place (e.g., a dataset mounted into the jail for easier snapshots) then you will need to change it using sysrc
sysrc radarr_data_dir="DIR_YOU_WANT"
Reminder: If you are using an existing location then you will manually need to either: change the ownership to the UID/GID radarr uses AND/OR add radarr to a GID that has write access.
Almost done, let's start the service:
service radarr start
If everything went according to plan then radarr should be up and running on the IP of the jail (port 7878)!
You can now safely close the shell
The service appears to be running but the UI is not loading or the page is timing out
allow_mlock is enabled in the jailSystem.NET.Sockets.SocketException (43): Protocol not supported
VNET turned on for your jail, ip6=inherit, or ip6=newThe service script should now work around the lack of VNET and/or IP6 thus removing the requirement for VNET or ip6=inherit
The Radarr team does not offer an official Docker image. However, a number of third parties have created and maintain their own.
These instructions provide generic guidance that should apply to any Radarr Docker image.
There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links.
The first is a problem because the download client will report a download's path as /torrents/My.Movie.2018/, but in the Radarr container that might be at /downloads/My.Movie.2018/. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.
Most Docker images suggest paths like /movies and /downloads. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside the container. Some also recommend paths for the download client container that are different from the Radarr container, like /torrents.
The best solution is to use a single, common volume inside the containers, such as /data. Your Movies would be in /data/Movies, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet.
If this advice is not followed, you may have to configure a Remote Path Mapping in the Radarr web UI (Settings › Download Clients).
Permissions and ownership of files is one of the most common problems for Radarr users, both inside and outside Docker. Most images have environment variables that can be used to override the default user, group and umask, you should decide this before setting up all of your containers. The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Radarr will need read and write to the download folders as well as the final folders.
For a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.
To install and use these Docker images, you will need to keep the above in mind while following their documentation. There are many ways to manage Docker images and containers too, so installation and maintenance of them will depend on the route you choose.
Sample config examples for configuring Radarr to be accessible from the outside world through a reverse proxy.
These examples assumes the default port of
7878and that you set a baseurl ofradarr. It also assumes your web server i.e nginx and Radarr running on the same server accessible atlocalhost(127.0.0.1). If not, use the host IP address or hostname instead for the proxy pass directive.
Add the following configuration to nginx.conf located in the root of your Nginx configuration. The code block should be added inside the server context. Full example of a typical Nginx configuration
If you're using a non-standard http/https server port, make sure your Host header also includes it, i.e.:
proxy_set_header Host $host:$server_port
location ^~ /radarr {
proxy_pass http://127.0.0.1:7878;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
}
# Allow the API External Access via NGINX
location ^~ /radarr/api {
auth_basic off;
proxy_pass http://127.0.0.1:7878;
}
A better way to organize your configuration files for Nginx would be to store the configuration for each site in a separate file.
To achieve this it is required to modify nginx.conf and add include subfolders-enabled/*.conf in the server context. So it will look something like this.
server {
listen 80;
server_name _;
# more configuration
include subfolders-enabled/*.conf
}
Adding this line will include all files that end with .conf to the Nginx configuration. Make a new directory called subfolders-enabled in the same folder as your nginx.conf file is located. In that folder create a file with a recognizable name that ends with .conf. Add the configuration from above from the file and restart or reload Nginx. You should be able to visit Radarr at yourdomain.tld/radarr. tld is short for Top Level Domain
Alternatively you can use a subdomain for radarr. In this case you would visit radarr.yourdomain.tld. For this you would need to configure a A record or CNAME record in your DNS.
Many free DNS providers do not support this
By default Nginx includes the sites-enabled folder. You can check this in nginx.conf, if not you can add it using the include directive. And really important, it has to be inside the http context. Now create a config file inside the sites-enabled folder and enter the following configuration.
For this configuration it is recommended to set baseurl to '' (empty). This configuration assumes you are using the default
7878and Radarr is accessible on the localhost (127.0.0.1). For this configuration the subdomainradarris chosen (line 5).
If you're using a non-standard http/https server port, make sure your Host header also includes it, i.e.:
proxy_set_header Host $host:$server_port
server {
listen 80;
listen [::]:80;
server_name radarr.*;
location / {
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_redirect off;
proxy_http_version 1.1;
proxy_pass http://127.0.0.1:7878;
}
}
Now restart Nginx and Radarr should be available at your selected subdomain.
This should be added within an existing VirtualHost site. If you wish to use the root of a domain or subdomain, remove radarr from the Location block and simply use / as the location.
Note: Do not remove the baseurl from ProxyPass and ProxyPassReverse if you want to use / as the location.
<Location /radarr>
ProxyPreserveHost on
ProxyPass http://127.0.0.1:7878/radarr connectiontimeout=5 timeout=300
ProxyPassReverse http://127.0.0.1:7878/radarr
</Location>
ProxyPreserveHost on prevents apache2 from redirecting to localhost when using a reverse proxy.
Or for making an entire VirtualHost for Radarr:
ProxyPass / http://127.0.0.1:7878/radarr/
ProxyPassReverse / http://127.0.0.1:7878/radarr/
If you implement any additional authentication through Apache, you should exclude the following paths:
/radarr/api/It is possible to run multiple instances of Radarr. This is typically done when one wants a 4K and 1080p copy of a movie. Note that you can (and probably should) review TRaSH's guide and configure Radarr to use a second Radarr as a list. This is helpful if you wish to keep both in sync.
The following requirements should be noted:
-data= or /data= argument passedThis guide will show you how to run multiple instances of Radarr on Windows using only one base installation. This guide was put together using Windows 10; if you are using a previous version of Windows (7, 8, etc.) you may need to adjust some things. This guide also assumes that you have installed Radarr to the default directory, and your second instance of Radarr will be called Radarr-4K. Feel free to change things to fit your own installations, though.
nssm stop Radarrsc config Radarr binpath= "C:\ProgramData\Radarr\bin\Radarr.exe -data=C:\ProgramData\Radarr"This command tells the original instance of Radarr to explicitly use
C:\ProgramData\Radarr for its data directory. If you didn't use the
default Radarr install, or if your data folder is somewhere else, you
may have to change your paths here.
C:\ProgramData\Radarr-4Knssm install Radarr-4K. A popup window will open where you can type yourC:\ProgramData\Radarr\bin\Radarr.exeC:\ProgramData\Radarr\bin-data=C:\ProgramData\Radarr-4KNote that Arguments points to the new folder created in step 1.
This is crucial, as it keeps all the data files from both instances in
separate locations.
/data= argument to allow multiple instances%appdata%\Microsoft\Windows\Start Menu\Programs\Startup and edit the existing shortcut if needed.C:\ProgramData\Radarr\bin\Radarr.exe /data=C:\ProgramData\Radarr-4KRadarr-4K and finish the wizard.Port Number from 7878 to a different port e.g. 7879 so Radarr and Radarr4k do not conflict<Branch>nonexistent</Branch>Configuring the NSSM Exit Action correctly should allow Radarr to update and restart multiple instances with no additional scripts.
If the restart delay is not configured by default it will restart the instance immediately.
This can prevent updates from being applied and can result in the following errorRadarr was restarted prematurely by external process.
Run with highest privileges
On Launch5 or 10 minutesStart a Programpowershell-File D:\RadarrInstancesChecker.ps1
################################################################################################
### RadarrInstancesChecker.ps1 ###
################################################################################################
### Keeps multiple Radarr Instances up by checking the port ###
### Please use Radarr´s Discord or Reddit for support! ###
### https://wiki.servarr.com/radarr/installation#windows-multi ###
################################################################################################
### Version: 1.1 ###
### Updated: 2020-10-22 ###
### Author: reloxx13 ###
################################################################################################
### SET YOUR CONFIGURATION HERE ###
# Set your host ip and port correctly and use your service or scheduledtask names!
# (string) The type how Radarr is starting
# "Service" (default) Service process is used
# "ScheduledTask" Task Scheduler is used
$startType = 'Service'
# (bool) Writes the log to C:\Users\YOURUSERNAME\log.txt when enabled
# $false (default)
# $true
$logToFile = $false
$instances = @(
[pscustomobject]@{ # Instance 1
Name = 'Radarr-V3'; # (string) Service or Task name (default: Radarr-V3)
IP = '192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
Port = '7873'; # (string) Server Port where Radarr runs (default: 7873)
}
[pscustomobject]@{ # Instance 2
Name = 'Radarr-4K'; # (string) Service or Task name (default: Radarr-4K)
IP = '192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
Port = '7874'; # (string) Server Port where Radarr runs (default: 7874)
}
# If needed you can add more instances here... by uncommenting out the below lines
# [pscustomobject]@{ # Instance 3
# Name='Radarr-3D'; # (string) Service or Task name (default: Radarr-3D)
# IP='192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
# Port='7875'; # (string) Server Port where Radarr runs (default: 7875)
# }
)
### DONT CHANGE ANYTHING BELOW THIS LINE ###
###
# This function will write to a log file or in console output
###
function Write-Log
{
#Will write to C:\Users\YOURUSERNAME\log.txt
Param(
$Message,
$Path = "$env:USERPROFILE\log.txt"
)
function TS { Get-Date -Format 'hh:mm:ss' }
#Console output
Write-Output "[$(TS)]$Message"
#File Output
if ($logToFile)
{
"[$(TS)]$Message" | Tee-Object -FilePath $Path -Append | Write-Verbose
}
}
Write-Log 'START ====================='
$instances | ForEach-Object {
Write-Log "Check $($_.Name) $($_.IP):$($_.Port)"
$PortOpen = ( Test-NetConnection $_.IP -Port $_.Port -WarningAction SilentlyContinue ).TcpTestSucceeded
if (!$PortOpen)
{
Write-Log "Port $($_.Port) is closed, restart $($startType) $($_.Name)!"
if ($startType -eq 'Service')
{
Get-Service -Name $_.Name | Stop-Service
Get-Service -Name $_.Name | Start-Service
}
elseif ($startType -eq 'ScheduledTask')
{
Get-ScheduledTask -TaskName $_.Name | Stop-ScheduledTask
Get-ScheduledTask -TaskName $_.Name | Start-ScheduledTask
}
else
{
Write-Log '[ERROR] STARTTYPE UNKNOWN! USE Service or ScheduledTask !'
}
}
else
{
Write-Log "Port $($_.Port) is open!"
}
}
Write-Log 'END ====================='
-data= argument passed.systemctl stop radarrBelow is an example script to create a Radarr4K instance. The below systemd creation script will use a data directory of
/var/lib/radarr4k/. Ensure the directory exists or modify it as needed.
cat << EOF | sudo tee /etc/systemd/system/radarr4k.service > /dev/null
[Unit]
Description=Radarr4k Daemon
After=syslog.target network.target
[Service]
User=radarr
Group=media
Type=simple
ExecStart=/opt/Radarr/Radarr -nobrowser -data=/var/lib/radarr4k/
TimeoutStopSec=20
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl -q daemon-reload
sudo systemctl enable --now -q radarr4k