#Install sonarr on qnap how to
#Install sonarr on qnap password
#Install sonarr on qnap free

The default ports for the plugins are as followsįirst we will begin by configuring sabnzbd. The plugins can be found by typing in the jail ip address with the appropriate port ex: 192.168.1.56:8080 Now we are done configuring the plugins in the CLI and we can move onto configuring them from the web GUI. First we will create a dataset for our media by navigating to storage > pools > Add Dataset.

#Install sonarr on qnap free

If you are able to find a solution that fixes this issue feel free to post a reply.

#Install sonarr on qnap password

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. After doing research, it seems that many users are having issues with SMB permissions after the 11.3 update. Sometimes it will work as expected, and then other times I cannot connect no matter what credentials I am using. However I have had multiple issues with permissions in windows.

In order to use these plugins properly, you will need to have a usenet provider account, and indexers.ĭISCLAIMER: This guide follows the steps for permissions as recommended by FreeNAS in this video. 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. Makes life much easier than remembering all the random ports all the services use.This is an updated version of this guide for 11.1-U5 I suggest just picking a range of ports (eg 13500-13525), and running all your Dockers with EXTERNAL ports in that range. Internal port is expected to stay the same so don't change these. You can change the external port to whatever you like.

#Install sonarr on qnap how to

It's so much easier once you understand how to format everything. Honestly it's better to spend a few hours getting comfortable using SSH to paste the docker run command. Use it as a reference as you create the docker in container station. You'll have the ability to change ports / env variables and paths again.Ĭopy the docker run command from GitHub or dockerhub into notepad++ and change everything to suit your system. Either create a backup of it, delete it, restore your backup or just start from scratch again.

You have to scrub it and do it again with your new ports. Once a docker is created you can't change the internal or external ports on qnap (or perhaps not a qnap quirk?). You might not care about this, but you may as well create the /config or /data share as all your containers are already utilising it, you just aren't giving yourself access. But what if the apps are down and you want to view the log? or its all busted and you need access to your auto backups? Again, they are in the image, and can possibly be accessed via SSH but its a pain.įor some containers (eg delugvpn) you need to manually edit config files or provide openVPN files, you can't easily do this without access to your /config folder.Īn added bonus is you can use scripting to backup the config location to the cloud, so you won't lose everything is the system goes down. I think this also only works if the container is online.įor Sonarr and Radarr it isn't massive issue, as you can access logs in the apps. If you don't do this, then upon pulling the image the container will create the /config folder anyway, but you can only access it via exec into the image via SSH (pain in the ass). config /share/Container/container-config/sonarrv3 Read/Write I have a share called Container so for me CS looks like this Shared Folders You are supposed to create a /config folder somewhere easily accessible on your NAS host for each docker to store its data.