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 FlareSolverr to the Extras section of the guide | 10/11/2023 |
| Guide amended to include FlareSolverr into the Project and step through adding this all to GlueTUN | 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.
Let’s Begin
This guide makes the assumption that you have already setup GlueTUN and looking to layer this into the existing Project. See the left menu on how to do that with either Deluge or qBittorrent.
Folder Setup
Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.
/docker/prowlarr
Container Manager
Next we are going to set stop and edit the existing GlueTUN VPN project in Container Manager.
Open up container manager and in the Project section select the `vpn-project` then Action > Stop.
Once the project has stopped click into it and select the YAML Configuration tab and scroll to the bottom of it as we are going to add the additional configuration for Prowlarr and FlareSolverr.
First we are going to add the extra required ports to the appropriate section at the top of the compose. Copy them and paste them as per the screenshot.
- 8191:8191/tcp #flaresolverr
- 9696:9696/tcp #prowlarr
Next we are going to drop in our docker compose configuration copy all the code in the box below and paste below your existing code.
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
network_mode: service:gluetun
depends_on:
gluetun:
condition: service_healthy
security_opt:
- no-new-privileges:true
restart: always
flaresolverr:
image: flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
network_mode: service:gluetun
depends_on:
gluetun:
condition: service_healthy
security_opt:
- no-new-privileges:true
restart: alwaysEnvironment Variables
We need to make some changes in order for the added containers to have the correct permissions to save their config files and know where you are in the world.
| 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 |
Once you have amended these we can Build the Project again.
Click Save and then Click OK.
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
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)
Buy Me a Coffee or a Beer
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 get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.
I keep getting errors on my prowlarr that my proxy (Flaresolverr) is unavailable. It works intermittently, but then it randomly will throw this error. I have it setup with http://172.20.0.1:8191/ (tried the other IPs and the test outright fails where 172.20.0.1 at least allows the test to be successful to save the proxy.
Anyone else see something similar?
Thanks!
Hey Dr,
Thanks for all the amazing guides! have set Prowlarr up without VPN following your guides. Prowlarr is succesfully connectted to Radarr, Sonarr and Lidarr with synobridge (172.20.0.1).
I’m running into a problem when trying to add indexers, like 1337x. I keep getting the error:
“Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. The SSL connection could not be established, see inner exception.”
I was able to add Nyaa.si succesfully, but all others I have tried so far give the same error. I tried adding 1337x.to with Flaresolverr (added the tag on the Add indexer screen), but the same error appear.
Do you know that the issue might be? Thanks!
I
I would initially check through your network and disable ipv6 where ever it is enabled or if set to auto disable it. This would be in the DSM network settings, and on your router or DHCP server.
This always seems to come up with Prowlarr for some people. Try that to start with.
Hey, i had the same issue, it seems that some ISPs block indexers such as 1337x. to fix this all i had to do was connect my Prowlarr to the GlueTUN VPN that i created following the Docs “qBittorrent with GlueTUN VPN” guid.
additionally i had trouble getting it to work with the VPN and just added Prowlarr and FlareSolverr to the same Yaml file that i used to create Qbit and Gluetun.
Hope this helps! :3
Thanks!
I ended up doing the same (prowlarr and flaresolver) in the same project and using Gluetun VPN. It’s all working perfectly now!
@Dr. Frankenstein, thanks again for all your help 🙂
When I paste the VPN-enabled Prowlerr YAML at the bottom of the Gluetun YAML, it says “Property restart is not allowed” and highlights “restart: true”. Why?
Apologies – remove that line Container Manager doesn’t support it. I will change it now.
Think you could do a guide for setting up flaresolverr? A couple indexers I use need cloudflare solutions, but just running the flaresolverr image using googled instructions isn’t working for me, nor is trying to follow the general steps used for other containers.
Hey let me see how it works and see if I can get it as an optional extra.
+1, got everything to work but indexes are not great with the cloudflare issues.
Amazing consistent guides btw, best one I have seen.
Love your tutorials!
Few things that may be helpful:
1) a general overview of the components involved. E.g., I was somewhat confused about the difference between media management (sonarr,radarr), index servers (prowlarr, spotweb, etc.), and individual indexers.
2) in prowlarr: how to connect it to radarr (settings->apss->radarr) and where to get the API key
Hey just catching up on comments! – There is quite a bit to explain from a setup perspective and I try to just cover the basics on getting the container and correct paths running. There is great documentation on https://wiki.servarr.com/ that goes through all the settings.