Important or Recent Updates
| Historic Updates | Date |
|---|---|
| Updated guide for Container Manager | 22/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. | 25/10/2023 |
| Added FlareSolver to the Extras section of the guide | 10/11/2023 |
| Guide amended to integrate Flaresolverr as a core piece of the project | 09/12/2023 |
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.
/docker/projects/prowlarr-flaresolverr-compose
/docker/prowlarr
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:
| Section | Setting |
|---|---|
| Project Name: | prowlarr-flaresolverr |
| Path: | /docker/projects/prowlarr-flaresolverr-compose |
| 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.
services:
linuxserver-prowlarr:
image: linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/prowlarr:/config
ports:
- 9696:9696/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: always
flaresolverr:
image: flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
ports:
- 8191:8191
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: alwaysEnvironment 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.
| Variable | Value |
|---|---|
| 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 wikipedia.org/wiki/List_of_tz_database_time_zones |
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 the Synology Firewall enabled please see this additional guide for further info on exceptions and correct set up.
Container set up complete
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
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.
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 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 ‘http://172.20.0.1’. (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.
Hi,
I have to thank you again for all the tutorials you’ve posted, I have followed a few of them and no issues when setting up the docker containers. I have a question in regards to FlareSolverr, I can see that there’s no volumes under the FlareSolverr YML, I was wondering where does the FlareSolverr gets saved? I couldn’t find the files for FlareSolverr.
Thank you.
Hey, Flaresolverr doesn’t have any user configurable elements other than environment variables, as has not need to save configs so it just creates a disposible docker volume and this gets removed and recreated on an update.
what ports are you adding to the firewall exception?
why not add the IP/Subnet of the synobridge?
Hey, I will tweak the wording of the opening section for the Firewall to make it clear exceptions will be needed for any ports used in the guide. So in this case 9696 and 8191.. The synobridge exceptions are added within the original guide.https://drfrankenstein.co.uk/step-3-setting-up-a-docker-bridge-network-in-container-manager/
Your original guide is what I followed long ago. Adding the Synobridge IPs to the firewall exception to allow internal communication.
Should I replace the original exception with all the port numbers for internal communications?
Sorry. All external communications is lost When I removed the Synobridge IPs form the firewall and use the Port numbers.
The bridge IPs will allow the inter container communication, you just need to add the outward ports to be able to use them with the NAS IP address as the Firewall will be blocking them without any exceptions
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?
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!