Prowlarr in Docker on a Synology NAS

Please note if you are using DSM7.2 or higher you should use the Container Manager version of this guide from the menu.

This guide has reached the end of its updates as most people are now on the latest DSM update - This guide is correct as of 08/12/2023 however no further updates will be added.

What is Prowlarr?

Prowlarr is an application that combines your various indexers for torrents and Usenet into one place, it then syncs all the indexer settings automatically with Sonarr, Radarr etc.

Let’s Begin

In order for you to successfully use this guide please complete these two guides and come back here.

• Step 2: Setting up a restricted Docker user
• Step 3: Setting up a Docker Bridge Network

Downloading the Prowlarr Image

Open up Docker within DSM and navigate to the ‘Registry’ section and search for ‘prowlarr’ in the search box and download the Linux Server version

When asked make sure you choose ‘latest‘ from the list of available versions

You can check the status of the download over on the ‘Image’ tab.

Setting up the container

In Docker click on the ‘Image’ tab, in the list of your containers select the ‘Linuxserver Prowlarr’ image and click on ‘Launch’

You will be greeted with the Network screen, we will be using the ‘synobridge’ network we created earlier select it from the list and click Next.

General Settings

Next you will be greeted with the General Settings screen, this is where you can start specifying some of your preferences.

You can change the name of the container to anything you like, and you may want to enable Auto Restart as this will ensure Prowlarr starts automatically if you reboot your NAS.

Now click on the Advanced Settings button.

Environment (PGID,  PUID and Timezone)

Next we are going to set up a couple of environment variables that docker will use to allow the container access to our filesystem and also to tell it where we live in the world.

Click the Add button, and fill in the following details as per the table/screenshot, you will need to do one at a time.

Links / Execution Command

You do not need to set up anything on these tabs.

Press ‘Save’ to go back to the initial setup screen, then press ‘Next’

Port Settings

We won’t be changing any of the ports the container uses. You can repeat the ones shown on the right side of the settings page ‘Container Port’ onto the left side ‘Local Port’ once you have done this press ‘Next’.

Volume Settings

We will now be specifying the directories where Radarr will store its configuration files and where to find our media and downloads.

Click on Add Folder and create a new sub-folder called ‘prowlarr’ within the docker share then select this folder.

Now we need to specify where this folder will be mounted inside the container. As per the screenshot/table below:

Summary

You have now completed the setup of the container.

You will be shown an overall summary of the settings we have specified, this is a good time to double-check everything is correct. Finally, click on Done and the container should start to boot.

You should now be able to access Prowlarr via the IP of your NAS followed by the port 9696

e.g. 192.168.0.40:9696

Extras

FlareSolverr

More indexers are implementing Cloudflare protection that will block you accessing their site via a proxy such as Prowlarr. Flaresolverr has some magic ingredients to get around this issue can be added to the Prowlarr container yaml.

I have provided two examples below one for adding to Prowlarr outside of a VPN connection and the second is to add onto the GlueTUN container.

Non VPN

  flaresolverr:
    image: flaresolverr/flaresolverr:latest
    container_name: flaresolverr
    environment:
      - TZ=Europe/London
    ports:
      - 8191:8191
    network_mode: synobridge
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped

VPN (GlueTUN)

  flaresolverr:
    image: flaresolverr/flaresolverr:latest
    container_name: flaresolverr
    environment:
      - TZ=Europe/London
    network_mode: service:gluetun
    depends_on:
      gluetun:
        condition: service_healthy
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped
    
#Then add the ports to the GlueTUN container

      - 8191:8191

Once you have added this to your container you have a couple of extra steps.

As per the firewall section create another exception, then continue

Head into Prowlarr > Settings > Indexers > Click + then select FlareSolverr

Once added enter the details as per the screenshot below – ensure you keep note of the ‘Tags’ as this is what you will add to an actual indexer to tell it to use FlareSolverr

There are 3 possible connection options to use, try from top to bottom.

http://localhost:8191/
http://172.20.0.1:8191/
http://YOUR-NAS-IP:8191/

You then tag each indexer that requires FlareSolverr

FAQ

Prowlarr can’t connect to my Arrs

When setting up the connection between Prowlarr and Radarr/Sonarr/Lidarr some users have reported getting a time-out when using the NAS IP. If this happens try using the Gateway IP of the SynoBridge network, which should be ‘http://172.20.0.1’. (you can see this in the Docker UI in Networks) – I am not sure what is causing this issue for some and not others.

Looking for some help, join our Discord community

If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!

Buy me a beverage!

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.