FreeNAS: Radarr Manual Install

Install Radarr in FreeNAS
Radarr is an absolute essential tool to include in your FreeNAS setup and to have installed in a jail. Radarr is an independent fork of Sonarr, reworked for automatically downloading movies via Usenet and BitTorrent. Radarr can integrate directly into your media server setup and integrates directly with most modern download clients: uTorrent, Deluge, rTorrent, NZBGet, SABnzbd, qBittorrent, Transmission and many more. It will determine when the file has been downloaded an move it to the correct media folder to be picked up by media servers such as Plex and Emby. The project was inspired by other Usenet/BitTorrent movie downloaders such as CouchPotato. When first setting up FreeNAS it was Radarr that was causing me the most problems, largely because I had Radarr in its own jail and had problems with ensuring consistent path names in configs (qBittorent and Radarr) and ensuring that file permissions were correctly setup. This article will show you how to install Radarr within an existing jail (e.g. with your OpenVPN connection and a torrent client) in the most simple way to avoid path and file permission problems that I have previously experienced. With that, lets get on with a Radarr manual install by following the directions in the article.

UPDATE: I have updated this article for TrueNAS and you can read the TrueNAS: Radarr Manual Install article.

This article is part of my series of FreeNas setup, configuration and install articles.

Radarr Manual Install

First we need to make sure that everything is up to date using the following commands from the shell within the jail in which you are installing Radarr:

pkg update
pkg upgrade

Next we can get the package manager to install radarr with the following command:

pkg install radarr

Wait a couple of mintues for it to install Radarr and all it dependencies.

Radarr Setup

First we will need to enable the Radarr service and allow it to run at startup with the following command (again from within the jail’s shell):

sysrc "radarr_enable=YES"

I was having security problems, so I want Radarr to run as root, not as the user ‘radarr’ which it is set to as default. To do this I edited the /usr/local/etc/rc.d/radarr file and changed:

: ${radarr_user:=”radarr”}

to:

: ${radarr_user:=”root”}

Of course you can keep the users as ‘radarr’ or change it to whatever user you like, just will just need to pay close attention to the securities and how they relate to the securities in the larger FreeNAS system (e.g. match UIDs and GIDs).

Open the WebUI at IPADDRESS:7878

Ensuring Future Updates

We need to make sure Radarr knows where to run mono from for future updates. If you don’t do this step you will get an error like:

System.ComponentModel.Win32Exception: ApplicationName=‘mono’, CommandLine=’–debug /tmp/nzbdrone_update/NzbDrone.Update.exe 7274 /tmp/nzbdrone_update /usr/pbi/radarr-amd64/share/radarr/NzbDrone.exe /data=/var/db/radarr/nobrowser’, CurrentDirectory=’’, Native error= Cannot find the specified file

The issues is a path problem and thankfully the fix is quite simple. Simply enter the shell of the jail running Radarr and enter the following command:

ln -s /usr/local/bin/mono /usr/bin/mono

Radarr Configuration

I won’t provide all the information on how to configure Radarr as there are a number of guides out there and they don’t need to be OS specific. I will however provide a couple tips which can help.

First, I had trouble for a while with qBittorrent removing the torrent when done. Radarr does not like it when you tell it to remove automatically (presumably as it needs time to note the download is complete and copy it). Instead, you need to tell qBittorrent to ‘pause’ when the download is complete.

From the qBittorrent web interface, go to Tools -> Options -> Bittorrent Tab. Under the ‘Share Ratio Limiting’ heading the drop box beside where it says ‘then’ select ‘pause them’. Now put a tick beside ‘Seed torrents until their ratio reaches’ and set the value to whatever you want. ‘0’ would mean it would pause as soon as the download is complete and ‘1’ would mean as soon as it has shared an amount equal to the size of the file. Using ‘0’ is frowned upon in the torrenting community. **Scroll to the bottom and click ‘Save’**

qBittorent Options
qBittorent Options

Second, when setting up Radarr with Jackett, you do not need to individually add each URL for each search provider. Instead copy one (by clicking the ‘Copy Torznab Feed’ button) and pasting it into URL location in the Radarr config as shown in the image below.

Radarr Config
Radarr Config

You will need to edit the URL put in by removing the name of the search provider embedded with the URL and replacing it with ‘all’ as shown below:

Replace:

http://x.x.x.x:9117/api/v2.0/indexers/torrentz/results/torznab/

with

http://x.x.x.x:9117/api/v2.0/indexers/all/results/torznab/

You will of course need to insert your API key and any other configuration necessary.

Conclusion

So with this short, simple and straight forwards article on the easiest way to manually install Radarr within an exising jail, you should now be off to the races in terms of automatically getting movies onto your Plex or Emby media server.

Happy Radarring.

~Raze42

Liked it? Take a second to support digiMoot on Patreon!

4 thoughts on “FreeNAS: Radarr Manual Install

  1. Hi. Thank you so much for the helpful guides. They have saved me endless hours of time. One problem I am having with both Radarr and Sonarr is that the command “ln -s /usr/local/bin/mono /usr/bin/mono” throws an error,
    “ln: /usr/bin/mono: Read-only file system Command: ln -s /usr/local/bin/mono /usr/bin/mono failed!”.
    Because of this, I am unable to update Sonarr or Radarr with the autoupdater because it throws the error “Error occurred while executing task ApplicationUpdate: ApplicationName=’mono’, CommandLine=’–debug /tmp/radarr_update/Radarr.Update.exe 17072 /tmp/radarr_update /usr/local/share/radarr/Radarr.exe /data=/usr/local/radarr /nobrowser’, CurrentDirectory=”, Native error= Cannot find the specified file”
    If there is a known solution to this issue, that would be great! Thank you in advance.

      1. After a lot of research, I was able to solve the issue. The /usr/bin file system was set to read-only in fstab.

Leave a Reply

Your email address will not be published.