[HOW TO] Install and configure sonarr, radarr, transmission and sabnzbd (11.3-U3.2)

[IgJ]

Can someone point me in the right direction or provide some instructions for configuring indexers?

The instruction mention "Under settings>indexers this is where you will want to add the indexers that you are subscribed to as mentioned in the beginning of the guide.".

I have everything, with the exception of indexers, setup and running.

Thanks, Goody.

Indexers are setup inside of Sonarr and Radarr. That would be from the Web GUI, very simple once you find where. But I recommend adapting these instructions to install Jackett and NZBHydra as per your needs since they can centralize indexing for Sonarr and Radarr for you. It should be pretty straightforward to setup but you can probably find an individual guide from them if you search.

 

[Selassie]

This is an updated version of this guide for 11.1-U5

In the previous guide there ended up being a lot of questions about permissions, so I'll include creating the dataset and share from the beginning in this guide.

In order to use these plugins properly, you will need to have a usenet provider account, and indexers.

DISCLAIMER: This guide follows the steps for permissions as recommended by FreeNAS in this video. However I have had multiple issues with permissions in windows. Sometimes it will work as expected, and then other times I cannot connect no matter what credentials I am using. After doing research, it seems that many users are having issues with SMB permissions after the 11.3 update. Right now I currently recommend either allowing guest access, or adding the same username and password that you use in windows to provide passthrough authentication. If you are able to find a solution that fixes this issue feel free to post a reply.

• First we will create a dataset for our media by navigating to storage > pools > Add Dataset

• Name the dataset and since we are using windows in this guide, set the share type to SMB. Leave all other options as default.

• Next we will add a windows share by navigating to Sharing > Windows Shares (SMB) > ADD

• Select the path of the dataset that we created, and leave the other options as default.

NOTE: If you do not want to bother with permissions, you may select allow guest access. This will allow any user on your network to make changes to the files. Use at your own risk.

• Next we want to create the login credentials that we want will be using in windows and add that to the dataset. I prefer to create a group named users and add all new user accounts to that group just to keep things clean.

Navigate to Accounts > Groups > ADD.

• Choose whatever group number you would like and name it.

• Next navigate to Accounts > Users > Add.

• Enter the name of the user, then the username that you would like to use in windows, and your password. Uncheck the new primary group box, and select users as the primary group. Leave all other options as default and click save.

• Next we need to add that user to the dataset by navigating to Storage > Pools > Edit ACL.

• Here we will select ADD ACL ITEM, and then a new entry will appear at the bottom. Now we want to add the user we just created by selecting Who = User, and User = computerlogin. Leave all other options as default.

NOTE: You can change the permissions to read only if you are adding a user that you want to have access, but do not want to have the ability to change anything. Also if this is an existing dataset, you can select Apply permissions recursively in order to make sure this user has access to all existing files and folders.

• Next navigate to the share by opening windows explorer and entering "\\ipaddress" in the address bar.

Here you will see the shares you have configured

• Right click the share we configured earlier and select map network drive. Select connect using different credentials.

• Here you will select More choices > Use a different account. Then you will enter the username and password that we created earlier in freenas.

NOTE: If you do not wish to repeat this at any point, select Remember my credentials before continuing.

Now your new windows share is mapped as a drive, and you should be able to access it.

Now that we have our media share setup, we are going to create a new group and user that our plugins are going to use.

• Go to Accounts > Groups > Add and take note of the group ID and name. In this case we will do 900 and testnewmedia.

Note: You can choose whatever group ID and name you like, however you will need to make sure you continue to use the same ID and name in all places from here forward.

• Next we will make a user to match the group by navigating to Accounts > Users > Add. We need to make sure the username and ID matches the group name and ID. The password can be set to anything you like. Ensure that you do not have the New Primary Group box checked. All other options can be left as default.

View attachment 39862

• Next we need to add this user to our media share. Navigate to Storage > Pools > Edit ACL. You will select Add ACL Item and then choose user and testnewmedia. Leave the other options for this entry as default. Make sure you select Apply permissions recursively if you have any existing items in the share.

View attachment 39864

Next we will go ahead and create the jails for each of our plugins. Navigate to Jails > Add and then it will bring a wizard. On the first step select the default jail type, and then the release that corresponds with your version of freenas.

View attachment 39865

• On the second step we need to select the proper network configuration. Select the VNET Option, and then on IPv4 Interface select vnet0. Enter an IPv4 Address to create an address that is not already in use on your network. Under IPv4 select the Netmask the corresponds with your network (usually 24). Under IPv4 Default Router enter the IP address of your router. Leave all other options as default. Repeat this for each plugin that you want to install.

• Once this is complete you should have 4 jails in the down state.

• Before starting them, I recommend going to edit each jail and enabling the Auto-start option. This will ensure that your plugins start automatically in the event of a reboot.

View attachment 39869

• Next we need to add our media share to give the jail access. Select the dropdown for the jail and select mount points. Once here select Actions > Add and then select the path for the share we created. Your destination should be /mnt/testmedia. Leave Read-Only unchecked. Repeat this for each jail we created.

View attachment 39871

• Once you have the mount point added it should look like this.

• Now that the jails are all configured, we can turn them all on by selecting the check box for each one and selecting the start button.

View attachment 39870

• Now we will need to work through the command line to install the plugin and configure it. This can be done through putty, or you can simply access it directly by going to the jail dropdown and selecting shell. I will be using putty in this guide.
• Once you have logged into freenas, you can elevate your user to root priveleges by typing
  Code:

  sudo su -

• Once you are in the root of FreeNAS you can type
  Code:

  iocage list

  to see all of the jail information.

• To access the jail type
  Code:

  iocage console testsonarr

  .
• Now that we are in the jail we are going to create our directories by running the following commands.

Code:

cd /mnt/testmedia
mkdir downloads
cd downloads
mkdir sabnzbd transmission
cd sabnzbd
mkdir complete incomplete
cd complete
mkdir movies tvshows
cd\

• Next we need to make sure the package system is up to date by running the following commands.

Code:

pkg update
pkg upgrade

• Next we are going to install the plugin and a text editor by running the following commands.

Code:

pkg install nano
pkg install sonarr

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these command.

Code:

sysrc sonarr_enable=YES
service sonarr start

• Now we will create the user that we added to the media share within the jail and give the plugin this user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service sonarr onestop
chown -R testnewmedia:testnewmedia /usr/local/sonarr
sysrc 'sonarr_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/sonarr
service sonarr start

This completes what we need to configure from the CLI for sonarr, and now we will move on to radarr.

• Once we are in the CLI for the radarr jail, we will continue by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and radarr with the following commands.

Code:

pkg install nano
pkg install radarr

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc radarr_enable=YES
service radarr start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service radarr onestop
chown -R testnewmedia:testnewmedia /usr/local/radarr
sysrc 'radarr_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/radarr
service radarr start

This completes what we need to configure from the CLI for radarr, and now we will move on to sabnzbd.

• Once we are in the CLI for the sabnzbd jail, we will continute by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and sabnzbd with the following commands.

Code:

pkg install nano
pkg install sabnzbdplus

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc sabnzbd_enable=YES
service sabnzbd start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service sabnzbd onestop
chown -R testnewmedia:testnewmedia /usr/local/sabnzbd
sysrc 'sabnzbd_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/sabnzbdplus
chown -R testnewmedia:testnewmedia /var/run/sabnzbd
service sabnzbd start

• Now we need to change the following line of code in the sabnzbd config by running the following command.

Code:

nano /usr/local/sabnzbd/sabnzbd.ini

• Change the host line to host = 0.0.0.0 This will enable you to access sabnzbd on your jail ip address. Save changes by typing ctrl+shift+x. Confirm with Y then enter.

• Next start and stop sabnzbd with the following commands.

Code:

service sabnzbd onestop
service sabnzbd start

This completes what we need to configure from the CLI for sabnzbd, and now we will move on to transmission.

• Once we are in the CLI for the transmission jail, we will continue by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and transmission with the following commands.

Code:

pkg install nano
pkg install transmission

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc transmission_enable=YES
service transmission start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service transmission onestop
chown -R testnewmedia:testnewmedia /usr/local/etc/transmission
sysrc 'transmission_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/transmission
service transmission start

• Now we need to stop the transmission service and change the following line of code in the sabnzbd config by running the following command.

Code:

service transmission onestop
nano /usr/local/etc/transmission/home/settings.json

• Change the "'rpc-whitelist-enabled': true" line to false.

• Next start transmission with the following commands.

Code:

service transmission start

Now we are done configuring the plugins in the CLI and we can move onto configuring them from the web GUI. Save changes by typing ctrl+shift+x. Confirm with Y then enter.

the plugins can be found by typing in the jail ip address with the appropriate port ex: 192.168.1.56:8080
The default ports for the plugins are as follows
Sabnzbd: 8080
Sonarr: 8989
Radarr: 7878
Transmission: 9091

First we will begin by configuring sabnzbd.

in the setup wizard it will prompt you to enter your usenet server information. If this is not done here, it can be done under config>servers. (be sure to test the connection also)

Next under config>folders set the following.

• Temporary Download Folder = /mnt/media/downloads/sabnzbd/incomplete
• Completed Download Folder = /mnt/media/downloads/sabnzbd/complete

Next under config>categories set the following.

• Category = tv , Folder/Path = tv
• Category = movies , Folder/Path = movies

And lastly under config>switches set the following.

• Abort jobs that cannot be completed = [√]
• Action when encrypted RAR is downloaded = Abort
• Extra PAR2 Parameters = -t+

Now that we have sabnzbd setup, we will move on to transmission

Note: I do not personally use transmission to work with sonarr and radarr. As such I have not tested how the post processing and renaming is handled.

The only setting that needs to be set in transmission is to set the download path. Do this by navigating to edit preferences and then setting the path we created earlier /mnt/testmedia/downloads/transmission.

Now that transmission is setup, we can move on to sonarr, and radarr.

Note: Sonarr and Radarr are essentially the same, so I will only demonstrate how to setup Sonarr and these steps can be repeated for Radarr.

Note: With these steps select the test connection button each time you add an api to ensure that everything is working properly.

Under settings>indexers this is where you will want to add the indexers that you are subscribed to as mentioned in the beginning of the guide. It is recommended that you have 2 or 3 in the event that one crashes your service won't be interrupted.

Next under settings>download client this is where we will add sabnzbd and transmission.
Select add>sabnzbd

• name = sabnzbd
• host = IP address of sabnzbd
• api key = (found in sabnzbd config>general)

Selec add>Transmission

• name = transmission
• host = IP address of transmission

Next if you are using a media front end such as Kodi or Plex, you will want to select client and add what pertains to you. This will enable Sonarr and Radarr to update your library when a download is completed.

Repeat for radarr.

That's it, apart from some fine tuning according to your preferences, everything should be up and running.

I hope that this guide was helpful, and that you get good use out of it. I am planning on making a video to go along with it, and I will post that as soon as it's available.

I'm also happy to receive feedback on how this guide can be improved, or on any mistakes that you may have noticed.

A fantastic guide, a lot of hard work and well appreciated. However, since we are moving to Truenas Scale does anyone have a similar guide on how to do this with TrueNase Scale and Truecharts, as the entire plugin architecture has changed. In information on configuring Truecharts apps ad how to add additional host paths is very confusing.

 

[Norkz]

I tried this on the latest version of TrueNAS core and when I try to access the Jails it doesn't go to the page at all.
The release is 12.3 and all of the other settings are the same as described in this [ HOW TO ].
Can someone assist me on installing and configuring Sonarr, Radarr and a Torrent Jail for PLEX?

My discord is: Norkz#2594

I have been looking for other tutorials and the ones I found are mostly out of date and when I watched a video, I tried to add an Index to Radarr and it would say 'Unable to connect to indexer'.
Any help would be very much appreciated and thanks in advance.

Sincerely,
Norkz

 

[Selassie]

I tried this on the latest version of TrueNAS core and when I try to access the Jails it doesn't go to the page at all.
The release is 12.3 and all of the other settings are the same as described in this [ HOW TO ].
Can someone assist me on installing and configuring Sonarr, Radarr and a Torrent Jail for PLEX?

My discord is: Norkz#2594

I have been looking for other tutorials and the ones I found are mostly out of date and when I watched a video, I tried to add an Index to Radarr and it would say 'Unable to connect to indexer'.
Any help would be very much appreciated and thanks in advance.

Sincerely,
Norkz

you can try this link, it helped me a lot Install and configure sonarr, radarr, transmission and sabnzbd

 

[ify]

wish you had a setup for plex

 

[Selassie]

wish you had a setup for plex

I do have a Plex setup but I use Truenas for storage only and Ubuntu for the ‘arrs’

 

[shawndewet]

I can't get sonarr nor radarr services to start. Even though there is no error on the command line when I execute the command to start these services.
I understand from their wiki pages that the log files are here in the AppData folder here:
/home/$USER/.config/Sonarr or ~/.config/Sonarr

However, I can't figure out how to navigate to the indicated folder. I'm at the command line of my sonarr and radarr iocage jail as root....how do I get to the sonarr / radarr AppData folder referred to above?

 

[4ndrew]

Ive been trying to follow this guide, but I keep hitting roadbloks on the Radarr part where after I try to configure the user Radarr wont start again. The exact same process for Sonarr and SABnzbd worked fine, thoese services are up and running without an issue. My user and group are both mmanager btw. Any Idea what could be wrong? Ive tried to do it in a 12.3 Jail and a 13.1

 

[thewiz1906]

Ive been trying to follow this guide, but I keep hitting roadbloks on the Radarr part where after I try to configure the user Radarr wont start again. The exact same process for Sonarr and SABnzbd worked fine, thoese services are up and running without an issue. My user and group are both mmanager btw. Any Idea what could be wrong? Ive tried to do it in a 12.3 Jail and a 13.1

I'm having this exact same issue. Were you able to achieve any resolution here?

 

[r0x0x]

I'm having this exact same issue. Were you able to achieve any resolution here?

I'm having this same problem, there is a note in the message that is displayed after the radarr install that says to set allow_mlock=1 if you're running it in a jail but I tried setting that with sysrc allow_mlock=1 and I got the confirmation ->1 below but it didn't help got the still the same error

 

[ify]

I'm having this same problem, there is a note in the message that is displayed after the radarr install that says to set allow_mlock=1 if you're running it in a jail but I tried setting that with sysrc allow_mlock=1 and I got the confirmation ->1 below but it didn't help got the still the same error

Did you ever figure this out?

 

[ify]

Ive been trying to follow this guide, but I keep hitting roadbloks on the Radarr part where after I try to configure the user Radarr wont start again. The exact same process for Sonarr and SABnzbd worked fine, thoese services are up and running without an issue. My user and group are both mmanager btw. Any Idea what could be wrong? Ive tried to do it in a 12.3 Jail and a 13.1

Did you figure it out

 

[mattshieup]

i'm having the same issue with radarr. I've tried both the plugin or pkg install and config after. Sonarr and other work fine :(

 

[mattshieup]

so after debugging i found that the line causing radarr to crash is : sysrc 'radarr_user=medialib'

 

[mattshieup]

Hi,

So let me share it here. I'm so happy I eventually fixed Radarr. After comparing with other configs, I found it is using /var/run/radarr to start the service. Therefore, the following lines need to be sent also before starting the service:

chown -R testnewmedia:testnewmedia /var/run/radarr

 

[Ssri]

This is an updated version of this guide for 11.1-U5

In the previous guide there ended up being a lot of questions about permissions, so I'll include creating the dataset and share from the beginning in this guide.

In order to use these plugins properly, you will need to have a usenet provider account, and indexers.

DISCLAIMER: This guide follows the steps for permissions as recommended by FreeNAS in this video. However I have had multiple issues with permissions in windows. Sometimes it will work as expected, and then other times I cannot connect no matter what credentials I am using. After doing research, it seems that many users are having issues with SMB permissions after the 11.3 update. Right now I currently recommend either allowing guest access, or adding the same username and password that you use in windows to provide passthrough authentication. If you are able to find a solution that fixes this issue feel free to post a reply.

• First we will create a dataset for our media by navigating to storage > pools > Add Dataset

• Name the dataset and since we are using windows in this guide, set the share type to SMB. Leave all other options as default.

• Next we will add a windows share by navigating to Sharing > Windows Shares (SMB) > ADD

• Select the path of the dataset that we created, and leave the other options as default.

NOTE: If you do not want to bother with permissions, you may select allow guest access. This will allow any user on your network to make changes to the files. Use at your own risk.

• Next we want to create the login credentials that we want will be using in windows and add that to the dataset. I prefer to create a group named users and add all new user accounts to that group just to keep things clean.

Navigate to Accounts > Groups > ADD.

• Choose whatever group number you would like and name it.

• Next navigate to Accounts > Users > Add.

• Enter the name of the user, then the username that you would like to use in windows, and your password. Uncheck the new primary group box, and select users as the primary group. Leave all other options as default and click save.

• Next we need to add that user to the dataset by navigating to Storage > Pools > Edit ACL.

• Here we will select ADD ACL ITEM, and then a new entry will appear at the bottom. Now we want to add the user we just created by selecting Who = User, and User = computerlogin. Leave all other options as default.

NOTE: You can change the permissions to read only if you are adding a user that you want to have access, but do not want to have the ability to change anything. Also if this is an existing dataset, you can select Apply permissions recursively in order to make sure this user has access to all existing files and folders.

• Next navigate to the share by opening windows explorer and entering "\\ipaddress" in the address bar.

Here you will see the shares you have configured

• Right click the share we configured earlier and select map network drive. Select connect using different credentials.

• Here you will select More choices > Use a different account. Then you will enter the username and password that we created earlier in freenas.

NOTE: If you do not wish to repeat this at any point, select Remember my credentials before continuing.

Now your new windows share is mapped as a drive, and you should be able to access it.

Now that we have our media share setup, we are going to create a new group and user that our plugins are going to use.

• Go to Accounts > Groups > Add and take note of the group ID and name. In this case we will do 900 and testnewmedia.

Note: You can choose whatever group ID and name you like, however you will need to make sure you continue to use the same ID and name in all places from here forward.

• Next we will make a user to match the group by navigating to Accounts > Users > Add. We need to make sure the username and ID matches the group name and ID. The password can be set to anything you like. Ensure that you do not have the New Primary Group box checked. All other options can be left as default.

View attachment 39862

• Next we need to add this user to our media share. Navigate to Storage > Pools > Edit ACL. You will select Add ACL Item and then choose user and testnewmedia. Leave the other options for this entry as default. Make sure you select Apply permissions recursively if you have any existing items in the share.

View attachment 39864

Next we will go ahead and create the jails for each of our plugins. Navigate to Jails > Add and then it will bring a wizard. On the first step select the default jail type, and then the release that corresponds with your version of freenas.

View attachment 39865

• On the second step we need to select the proper network configuration. Select the VNET Option, and then on IPv4 Interface select vnet0. Enter an IPv4 Address to create an address that is not already in use on your network. Under IPv4 select the Netmask the corresponds with your network (usually 24). Under IPv4 Default Router enter the IP address of your router. Leave all other options as default. Repeat this for each plugin that you want to install.

• Once this is complete you should have 4 jails in the down state.

• Before starting them, I recommend going to edit each jail and enabling the Auto-start option. This will ensure that your plugins start automatically in the event of a reboot.

View attachment 39869

• Next we need to add our media share to give the jail access. Select the dropdown for the jail and select mount points. Once here select Actions > Add and then select the path for the share we created. Your destination should be /mnt/testmedia. Leave Read-Only unchecked. Repeat this for each jail we created.

View attachment 39871

• Once you have the mount point added it should look like this.

• Now that the jails are all configured, we can turn them all on by selecting the check box for each one and selecting the start button.

View attachment 39870

• Now we will need to work through the command line to install the plugin and configure it. This can be done through putty, or you can simply access it directly by going to the jail dropdown and selecting shell. I will be using putty in this guide.
• Once you have logged into freenas, you can elevate your user to root priveleges by typing
  Code:

  sudo su -

• Once you are in the root of FreeNAS you can type
  Code:

  iocage list

  to see all of the jail information.

• To access the jail type
  Code:

  iocage console testsonarr

  .
• Now that we are in the jail we are going to create our directories by running the following commands.

Code:

cd /mnt/testmedia
mkdir downloads
cd downloads
mkdir sabnzbd transmission
cd sabnzbd
mkdir complete incomplete
cd complete
mkdir movies tvshows
cd\

• Next we need to make sure the package system is up to date by running the following commands.

Code:

pkg update
pkg upgrade

• Next we are going to install the plugin and a text editor by running the following commands.

Code:

pkg install nano
pkg install sonarr

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these command.

Code:

sysrc sonarr_enable=YES
service sonarr start

• Now we will create the user that we added to the media share within the jail and give the plugin this user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service sonarr onestop
chown -R testnewmedia:testnewmedia /usr/local/sonarr
sysrc 'sonarr_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/sonarr
service sonarr start

This completes what we need to configure from the CLI for sonarr, and now we will move on to radarr.

• Once we are in the CLI for the radarr jail, we will continue by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and radarr with the following commands.

Code:

pkg install nano
pkg install radarr

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc radarr_enable=YES
service radarr start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service radarr onestop
chown -R testnewmedia:testnewmedia /usr/local/radarr
sysrc 'radarr_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/radarr
service radarr start

This completes what we need to configure from the CLI for radarr, and now we will move on to sabnzbd.

• Once we are in the CLI for the sabnzbd jail, we will continute by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and sabnzbd with the following commands.

Code:

pkg install nano
pkg install sabnzbdplus

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc sabnzbd_enable=YES
service sabnzbd start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service sabnzbd onestop
chown -R testnewmedia:testnewmedia /usr/local/sabnzbd
sysrc 'sabnzbd_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/sabnzbdplus
chown -R testnewmedia:testnewmedia /var/run/sabnzbd
service sabnzbd start

• Now we need to change the following line of code in the sabnzbd config by running the following command.

Code:

nano /usr/local/sabnzbd/sabnzbd.ini

• Change the host line to host = 0.0.0.0 This will enable you to access sabnzbd on your jail ip address. Save changes by typing ctrl+shift+x. Confirm with Y then enter.

• Next start and stop sabnzbd with the following commands.

Code:

service sabnzbd onestop
service sabnzbd start

This completes what we need to configure from the CLI for sabnzbd, and now we will move on to transmission.

• Once we are in the CLI for the transmission jail, we will continue by updating the package system with the following commands.

Code:

pkg update
pkg upgrade

• Next we will install the text editor and transmission with the following commands.

Code:

pkg install nano
pkg install transmission

• Next we need to enable the plugin to run when the jail starts up, and start the service manually for the first time with these commands.

Code:

sysrc transmission_enable=YES
service transmission start

• Next we need to create the new user and give the plugin that user with these commands.

Code:

pw useradd -n testnewmedia -u 900 -d /nonexistent -s /usr/sbin/nologin

service transmission onestop
chown -R testnewmedia:testnewmedia /usr/local/etc/transmission
sysrc 'transmission_user=testnewmedia'
chown -R testnewmedia:testnewmedia /usr/local/share/transmission
service transmission start

• Now we need to stop the transmission service and change the following line of code in the sabnzbd config by running the following command.

Code:

service transmission onestop
nano /usr/local/etc/transmission/home/settings.json

• Change the "'rpc-whitelist-enabled': true" line to false.

• Next start transmission with the following commands.

Code:

service transmission start

Now we are done configuring the plugins in the CLI and we can move onto configuring them from the web GUI. Save changes by typing ctrl+shift+x. Confirm with Y then enter.

the plugins can be found by typing in the jail ip address with the appropriate port ex: 192.168.1.56:8080
The default ports for the plugins are as follows
Sabnzbd: 8080
Sonarr: 8989
Radarr: 7878
Transmission: 9091

First we will begin by configuring sabnzbd.

in the setup wizard it will prompt you to enter your usenet server information. If this is not done here, it can be done under config>servers. (be sure to test the connection also)

Next under config>folders set the following.

• Temporary Download Folder = /mnt/media/downloads/sabnzbd/incomplete
• Completed Download Folder = /mnt/media/downloads/sabnzbd/complete

Next under config>categories set the following.

• Category = tv , Folder/Path = tv
• Category = movies , Folder/Path = movies

And lastly under config>switches set the following.

• Abort jobs that cannot be completed = [√]
• Action when encrypted RAR is downloaded = Abort
• Extra PAR2 Parameters = -t+

Now that we have sabnzbd setup, we will move on to transmission

Note: I do not personally use transmission to work with sonarr and radarr. As such I have not tested how the post processing and renaming is handled.

The only setting that needs to be set in transmission is to set the download path. Do this by navigating to edit preferences and then setting the path we created earlier /mnt/testmedia/downloads/transmission.

Now that transmission is setup, we can move on to sonarr, and radarr.

Note: Sonarr and Radarr are essentially the same, so I will only demonstrate how to setup Sonarr and these steps can be repeated for Radarr.

Note: With these steps select the test connection button each time you add an api to ensure that everything is working properly.

Under settings>indexers this is where you will want to add the indexers that you are subscribed to as mentioned in the beginning of the guide. It is recommended that you have 2 or 3 in the event that one crashes your service won't be interrupted.

Next under settings>download client this is where we will add sabnzbd and transmission.
Select add>sabnzbd

• name = sabnzbd
• host = IP address of sabnzbd
• api key = (found in sabnzbd config>general)

Selec add>Transmission

• name = transmission
• host = IP address of transmission

Next if you are using a media front end such as Kodi or Plex, you will want to select client and add what pertains to you. This will enable Sonarr and Radarr to update your library when a download is completed.

Repeat for radarr.

That's it, apart from some fine tuning according to your preferences, everything should be up and running.

I hope that this guide was helpful, and that you get good use out of it. I am planning on making a video to go along with it, and I will post that as soon as it's available.

I'm also happy to receive feedback on how this guide can be improved, or on any mistakes that you may have noticed.

@salsacalientemuy thanks you very much for your guide. I'm able to set this up in my HomeLab. This is so good.

But I had some obsticles i.e. radarr service was not able to start from the jail and even after troubleshooting that I was not able to access radarr UI.

After somemore investigation I found a solution in truenas community itself posted by @hertzsae in the discussion https://www.truenas.com/community/threads/guide-truenas-core-net-radarr-install.98583/#post-692997 which is:

Code:

bash
# Create the jail
iocage create -n "radarr" -r 12.2-RELEASE interfaces="vnet0:bridge0" defaultrouter="none" vnet="on" dhcp="on" bpf="yes" allow_raw_sockets="1" allow_mlock="1" boot="on"
iocage update radarr

# Update to the latest repo
iocage exec radarr "mkdir -p /usr/local/etc/pkg/repos"
iocage exec radarr "echo 'FreeBSD: {url: \"pkg+http://pkg.FreeBSD.org/\${ABI}/latest\"}' > /usr/local/etc/pkg/repos/FreeBSD.conf"
iocage exec radarr pkg update

# Install dependencies
iocage exec radarr pkg install -y radarr

# Mount storage and config
iocage exec radarr mkdir -p /config
iocage fstab -a radarr /mnt/Vol1/jail_config_data/radarr /config nullfs rw 0 0
iocage fstab -a radarr /mnt/Vol1/media /media nullfs rw 0 0

# Create media user and group
iocage exec radarr "pw groupadd media -g 816"
iocage exec radarr "pw useradd -n media -u 1001 -d /nonexistent -s /usr/sbin/nologin"

iocage exec radarr chown -R media:media /config

#iocage exec radarr vi /usr/local/etc/rc.d/radarr
iocage exec radarr sysrc "radarr_enable=TRUE"
iocage exec radarr sysrc radarr_user=media
iocage exec radarr sysrc radarr_group=media
iocage exec radarr sysrc radarr_data_dir="/config"
iocage exec radarr service radarr start

 

[mjayjock]

Thank you so much for this guide. It has really helped me to start to understand what is going on. I have been working on this for days, doing and redoing the installations. I am prone to typing errors and this has really slowed me up. I am being super careful about spelling and punctuation. I am to the point where I got sonarr up and running but radarr will not start: I get /usr/local/etc/rc.d/radarr: WARNING: failed to start radarr. It there anything else I can send you and where would I find it?

 

[mjayjock]

This guide is amazing and I appreciate all the time and effort you put into it.
I redid the installation for Radarr and early on the service stops and starts but when I do the last restart it chokes and will not start.
I thought, well I will let that go til later, and went on with the guide. SABnzb went perfect and I can see it on the web GUI and successfully configured it. Everything seemed to go good with the transmission install until I tried getting it up in the web GUI. No luck. I get "192.168.13.9 refused to connect". I changed allow_mlock from 0 to 1 (on advice from Frank) and the web GUI still will not come up. I stopped and started the service afterward, and checked the IP address and port (9090) - still no luck. I will go on with the sonarr installation by my batting average is pretty poor at this point.

 

[greenmonster]

Hi,

So let me share it here. I'm so happy I eventually fixed Radarr. After comparing with other configs, I found it is using /var/run/radarr to start the service. Therefore, the following lines need to be sent also before starting the service:

chown -R testnewmedia:testnewmedia /var/run/radarr

Thank you very much, this worked for me.

 

[phatcat]

Hi,

So let me share it here. I'm so happy I eventually fixed Radarr. After comparing with other configs, I found it is using /var/run/radarr to start the service. Therefore, the following lines need to be sent also before starting the service:

chown -R testnewmedia:testnewmedia /var/run/radarr

my hero