Skip to content

Prowlarr and FlareSolverr via GlueTUN VPN 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.
25/10/2023
Added FlareSolverr to the Extras section of the guide10/11/2023
Guide amended to include FlareSolverr into the Project and step through adding this all to GlueTUN09/12/2023
Removed the depends_on for gluetun as it’s not required04/01/2024
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.

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.

Folders
/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.

YAML
      - 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.

YAML

  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
    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
    security_opt:
      - no-new-privileges:true
    restart: always

Environment 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.

VariableValue
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 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.

Published inDockerSearch / Indexers 7.2Synology

41 Comments

  1. MrMeatball MrMeatball

    Hello!

    Are you putting prowlarr, FlareSolverr, sonarr, radarr, etc. in the same docker compose file as gluetun and qbittorrent?

    Thanks`

    • Dr_Frankenstein Dr_Frankenstein

      Hey MrMeatball

      So Radarr, Sonarr. Lidarr etc should not go on the VPN as recommended by the devs

      Prowlarr/Flaresolverr only needs the VPN if the indexers you are using are blocked in your country so require the VPN to bypass restrictions

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.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!