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.
Hi,
Great guide, first off. Really helpful.
I can’t seem to get the prowlarr working within the VPN YAML though. The terminal isn’t particularly helpful as it cuts off half the error, but it looks like I’m getting a warning about “Found orphan containers” when trying to build it, but I’m not familiar enough with Docker to know how to resolve that.
Is that something you’ve come across before?
If it mentions orphans take a look in the Container List to see if there is a container already created with the same name.
Hi, I am getting CONNECTION REFUSED error when trying to access prowlarr on
MYNASIP:9696. It was working in previous setup as standalone container, but when I upgraded and decided to follow the latest instructions as vpnproject can’t make it work.
I can access deluge no problem, but not prowlarr.
Looked at the logs tab in vpnproject page – no obvious errors
Any advice ?
Hey, can you also check the Prowlarr log to see if it has started up successfully as likely something is stopping the connection. Feel free to drop them to me via https://paste.drfrankenstein.co.uk and put the link in your reply.
I found the problem. Missed to add prowlarr ports to the gluten ports list. (THere are several places with the instructions for prowlarr, and one of them was not particularly clear about ports). After I added ports everything is working. Thanks for your guides.
Evening,
I keep getting “Map keys must be unique” and “Property flaresolverr is not allowed” when I attempt to add it t the vpn-project
TYA
PS: Merry xMAs
Howdy!
Keep in mind you need to add the main Prowlarr and FlareSolverr to the bottom of an existing Gluetun yaml. I think you are seeing these errors to due them being at the top..
Hi there
I added Prowler to the GlueTUN VPN project but I’m finding that the connection from Prowler to the indexers frequently breaks. Like you, I’m based in the UK, so I’m wondering if there really is a need to have Prowler on the VPN? How do you have it setup ie. on the VPN project or not?
I don’t know if moving Prowler will fix the connection issues to the indexers but it might be worth a go.
Great guides, by the way. Cheers
Hey, I have Prowlarr on the VPN as at this point Virgin Media and most other large ISPs block access to indexers.
I have not had any issues here other than using FlareSolverr for one particular indexer.
Just for clarity, for implementing FlareSolverr with a VPN would you edit/add it to the prowlarr-project YAML or the vpn-project YAML?
And would you change the YAML on prowlarr-project to “network_mode: service:gluetun” to run it on the VPN network or is it just as stated in the document?
Hey, I am working out a different layout for this Prowlarr guide as it has gained arms and legs since its original version, as some want / need prowlarr on the VPN and some don’t. So your question has highlighted a need to do a review…
In the interim
If you want to add Flaresolverr and Prowlarr to the VPN move both over to the GlueTUN project
1) Grab the VPN version of Flaresolverr in this guide
2) In the VPN qbittorrent guide the FAQ has the Prowlarr VPN yaml
3) add both of these to the VPN Project..
Thanks for the question if you get stuck let me know, and I can ping you an email.