Skip to content

Prowlarr and FlareSolverr in Container Manager on a Synology NAS

Important or Recent Updates
Historic UpdatesDate
Updated guide for Container Manager22/05/2023
Moved from UI setup to Project Setup which is more flexible and easier to maintain.
Added an addition element to the compose to restrict the container from gaining additional privilege.
Added FlareSolver to the Extras section of the guide10/11/2023
Guide amended to integrate Flaresolverr as a core piece of the project 09/12/2023
Historic Updates

What is Prowlarr and FlareSolverr?

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. FlareSolverr is an additional proxy which helps bypass Cloudflare protection that many indexers use.

If you plan on adding this to your GlueTUN VPN setup see the left menu for the alternative guide.

Let’s Begin

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

Folder Setup

Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.


Container Manager

Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.

In the next screen we will set up our General Settings, enter the following:

Project Name:prowlarr-flaresolverr
Source:Create docker-compose.yml

Next we are going to drop in our docker compose configuration copy all the code in the box below and paste it into line ‘1’ just like the screenshot.

What on earth is a Docker Compose?
Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.

    image: linuxserver/prowlarr:latest
    container_name: prowlarr
      - PGID=65432 #CHANGE_TO_YOUR_GID
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
      - UMASK=022
      - /volume1/docker/prowlarr:/config
      - 9696:9696/tcp
    network_mode: synobridge
      - no-new-privileges:true
    restart: always
    image: flaresolverr/flaresolverr:latest
    container_name: flaresolverr
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
      - 8191:8191
    network_mode: synobridge
      - no-new-privileges:true
    restart: always

Environment Variables

We need to make some changes in order for the container to have the correct permissions to save its configuration files and to have access to your media.

PUID(required) The UID you obtained in the user setup guide should be entered here
PGID(required) The GID you obtained in the user setup guide should be entered here
TZ(required) Your timezone

Click ‘Next’

You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.

On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!

The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.

The Project should now be running with a Green status

Firewall Exceptions

(Skip if you don’t have the Firewall configured)

If you have enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports used in this guide however it applies in the same way)

Also, I would like to refer people to the great guide on getting the Firewall correctly configured over on WunderTechs site.

Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.

Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.

You will now choose ‘Custom‘ and then the Custom button

Now select Destination from the drop-down menu, most web based containers require TCP access but check the guide as it will show the port and protocol. Then add comma separated ports. Then press OK.

Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.

You have now completed the Firewall changes and can continue with the guide.

Container set up complete

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


FlareSolverr Setup

Once you have set up Prowlarr and the Indexers you want to use, you can then add FlareSolverr to the ones that require it.

Go to 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.


You then tag each indexer that requires FlareSolverr


Prowlarr can’t connect to my Arrs or Download Client

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 ‘’. (you can see this in the Container Manager UI in Networks)

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.

Published inDockerSearch / Indexers 7.2Synology


  1. Stefan Stefan

    I’ve set up everything, but this final part is giving me trouble :-/ While connecting to Flaresolverr through Prowlarr, I receive a ‘Failed to test proxy’ error. Flare works fine independently (“FlareSolverr is ready!”). Any ideas for a solution?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, this seems to be a classic one with no rhyme or reason as to why it is blocking networking. I can only suggest trying stopping and starting the containers or a reboot to see if the network then bursts to life. Yhis feels like a Synology issue to be honest as we see it so often where containers on the same bridges within the same compose just refuse to talk with one another!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed. – writing Synology Docker Guides since 2016 – Join My Discord!