Wiki > Radarr
Radarr v0.2 is available as an app on your Manage page. Select Manage Apps next to the slot you want to use Radarr on. On this page, select
Add Radarr and provide your Whatbox password. After a short wait, you can click
Open Radarr to open Radarr. You can also access Radarr from your Manage page.
Radarr updates are currently managed by us. Attempting to use the built-in automatic update or restart functions in Radarr will fail. If you have attempted to update Radarr and Radarr is no longer accessible, connect to your slot via SSH, run
pkill -f Radarr.exe; rm ~/.config/Radarr/NzbDrone.pid and then restart Radarr and from your Manage page. The Manage page is also where you will find the WebUI for Radarr.
Connecting to rTorrent
Under Settings > Download Client, select to add a client with the + button and then select rTorrent. Enter the following information to connect to rTorrent:
Host: localhost Port: 443 URL Path: xmlrpc Use SSL: Yes Username: user Password: Your server password
Connecting to Transmission
You will need the Transmission daemon port from your Slot Info page.
Under Settings > Download Client, select to add a client with the + button and then select Transmission. Enter the following information to connect to Transmission:
Host: localhost Port: Daemon port as listed on your Slot Info page Username: user Password: Your server password
Connection to Deluge
You will need the Deluge WebUI address from your Slot Info page.
Make sure the Deluge WebUI has been enabled from the Settings link on your Manage page.
Under Settings > Download Client, select to add a client with the + button and then select Deluge. Enter the following information to connect to Deluge:
Host: localhost Port: 5 digit port from the end of your Deluge WebUI link, as listed on your Slot Info page. Password: Your server password Category: Leave blank if the Label plugin has not yet been enabled in the Deluge WebUI
If your Radarr webpage is not loading but on the Manage page shows that it is running and restarting the service does not resolve it check the logs and then kill and restart Radarr.
cd ~/.config/Radarr/logs (change directory to the log folder) tail radarr.txt (Displays last 10 lines / should see it complain that an instance is already running and then terminate itself) pkill -f Radarr.exe (terminate the frozen Radarr instance)
Once done with the steps above restart the Radarr instance from the Manage page.
Manually run another configuration
These instructions will create and run another configuration of Radarr alongside your existing configuration. You will need to manually access and manage additional configurations of Radarr, including starting them if your server is ever rebooted.
Make a second Radarr configuration directory
Make a second Radarr configuration file
Open the configuration file in nano
Copy the contents of the box below into the ~/.config/Radarr2/config.xml file, replacing any other configuration in the file
<Config> <Port>12660</Port> <UrlBase></UrlBase> <BindAddress>*</BindAddress> <SslPort>11330</SslPort> <EnableSsl>False</EnableSsl> <ApiKey></ApiKey> <AuthenticationMethod>None</AuthenticationMethod> <LogLevel>Info</LogLevel> <Branch>develop</Branch> <LaunchBrowser>False</LaunchBrowser> <UpdateAutomatically>False</UpdateAutomatically> </Config>
Save changes by pressing
Start Radarr in a screen session running in the background
screen -dmS Radarr2 mono --debug /usr/share/radarr/Radarr.exe -data=/home/user/.config/Radarr2 -c libcurl
Radarr will be accessible at http://server.whatbox.ca:12660 - Enable Authentication in Radarr's Settings -> General tab, using either authentication method with a strong username and password.
mono-based applications are inherently unstable and prone to crashing. Below are steps to take to have your Radarr instance automatically restart if it crashes, or if the server is rebooted.
Make a file to be used for the script.
Edit the file and enter the text below.
nano -w ~/radarr_restart.cron
#!/bin/bash if pgrep -fx "mono /usr/share/radarr/Radarr.exe -c libcurl" > /dev/null then echo "Radarr is running." else echo "Radarr is not running, starting Radarr" mono /usr/share/radarr/Radarr.exe -c libcurl fi exit
Save the file with Ctrl+x and the "y" and Enter to accept overwriting.
Make the script executable.
chmod +x ~/radarr_restart.cron
Open your crontab.
EDITOR=nano crontab -e
Enter the following text
@reboot /home/user/radarr_restart.cron >/dev/null 2>&1 */5 * * * * /home/user/radarr_restart.cron >/dev/null 2>&1
Save the crontab with Ctrl+x and the "y" and Enter to accept overwriting.
Radarr v3 (unstable)
You can follow these instructions to upgrade your existing Whatbox managed Radarr v0.2 installation to a self-managed Radarr v3 installation.
You must have Radarr v0.2 enabled and working on your slot's Manage Apps page before following these instructions.
Connect to your slot with SSH
Navigate to your Manage page, click
Manage Appsthen click
Ensure Radarr is disabled and all Radarr processes have been stopped
pkill -f -9 Radarr.exe
Create a backup of your current Radarr v0.2 config:
cp -r ~/.config/Radarr ~/.config/RadarrV2
Download the latest version
wget -O Radarr.nightly.V3.tar.gz "https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64"
Extract the archive
tar xzvf Radarr.nightly.V3.tar.gz
(Optional) Remove the installation archive
Update Mono's local user certificate storage. This is needed to access SSL/TLS servers from within Radarr v3
cert-sync --user /etc/ssl/certs/ca-certificates.crt
screen -dmS Radarr ~/Radarr/Radarr
(Optional) Change the automatic restart script to use the self-managed Radarr v3 installation
nano -w ~/radarr_restart.cron
#!/bin/bash if pgrep -fx "/home/user/Radarr/Radarr" > /dev/null then echo "Radarr is running." else echo "Radarr is not running, starting Radarr" screen -dmS Radarr /home/user/Radarr/Radarr fi exit
Save the file with
Enterto accept overwriting.