Skip to content

qBittorrent with OpenVPN in Docker on a Synology NAS

New guide using DSM7.111/05/2022
Added how to extract .rar files upon completion11/06/2022
Tweaked Firewall section to take into account TCP VPN Providers05/07/2022
Rewritten the TUN device section to now include script to enable at startup08/07/2022
Updated network settings you can now start the VPN via the DSM UI, however you will need to stop and start associated containers at the same time.30/07/2022

What are qBittorrent and OpenVPN?

qBittorrent is a torrent downloader and OpenVPN is the client application used to connect to your VPN provider.

Let’s Begin

In this guide I will take you through the steps to get qBittorrent up and running in Docker and a separate OpenVPN container. By having a separate container for the VPN connection we can use it in the future for other applications such as Prowlarr, this is useful if you have torrent indexers blocked in your country.

As the Synology DSM Docker GUI does not support some of the functions we need for this tutorial we will be using Docker Compose. This is not as complicated as it might seem!

In order for you to successfully use this guide please complete the three preceding guides

Folder Setup

Let’s start by getting a couple of folders set up for the containers to use. Open up Filestation and within the /docker share create a folder called ‘qbittorrent’ and one called ‘vpn’

VPN Package / TUN Device

We are now going to create the TUN device which allows the VPN connection to take place and then add a script to ensure it is automatically loaded whenever you reboot your NAS. Some people have not had to do the script part of the guide – your mileage may vary.

Synology VPN package

Head into the Package Center and download the Synology VPN Server package.

Once downloaded open up the VPN package and in the OpenVPN section enable the server.

Next click on Apply and you will receive this message regarding the Firewall and Router. We are not going to be forwarding any ports on our router, however if you do have the Firewall enabled on DSM we will be opening up an outbound port in a bit.

You can now disable the OpenVPN server by unchecking and applying the change again, as this has enabled the TUN, keep the package installed and running.

Setting up the start up script

First off credit to for this I am just using their code within this guide.

Open up Control Panel and then click on Task Scheduler

Next click on Create, Triggered Task then User Defined Script.

Now enter a name for the script – you can call it anything you like. The User must be ‘root’ and ‘Boot-up’ for the Event.

On the Task Settings tab copy and paste the code below in the ‘User-Defined script’ section. It will look like screenshot.

#!/bin/sh -e

insmod /lib/modules/tun.ko

You can now press OK and agree to the warning message. You can now move on to the next step.

Firewall (Optional Step if you have the Firewall Enabled)

If you have the Synology Firewall enabled and configured to block outgoing connections you will need to do this step. Otherwise, you will have issues with the VPN connecting to your provider. (please note the screenshot below does not show all the other rules you would normally have enabled)

Go into Control Panel > Security > Firewall

Click on Edit Rules and in the screen that appears click on ‘Create’

In the first screen select ‘Custom’

On the next screen we select the Type as ‘Destination Port’ and Protocol as ‘All’. In this example I am going to open up both 1194 and 1195 as some providers use UDP and some TCP and these are the most commonly used ports.

Click on OK and Apply the rule, and leave the ‘Source IP’ and ‘Action’ to their defaults on the original screen.

Configuration Files

In order for OpenVPN to connect to your provider we need to give it some key information for the connection. Due to the sheer amount of providers out there the information below will likely need to be tweaked based on your provider.

To keep this guide OS-agnostic I will be using the Synology Text Editor that can be installed via the package center. You can use your own preferred method such as using Notepad++ on Windows.

Open up Text Editor and create a new file, within this first file we are going to add our username and password for connecting to the VPN provider.

Now save this file in the ‘/docker/vpn’ folder and name it ‘vpn.auth’

The second file requires information from your VPN provider, they should have a number of OpenVPN configuration files for you to download on their website, usually split up into countries. Obtain one of these files.

Open up Text Editor and paste in the content of your providers .ovpn config file. It should look similar to the below however every provider is different!

We need to edit or add some key sections of this file as per the table below.

Original SettingUpdated SettingComments
auth-user-passauth-user-pass /vpn/vpn.authTells the container to get your login details from the vpn.auth file
persist-tun# persist-tunThis will ensure the connection is automatically reset if it fails
crl-verifycrl-verify /vpn/crl.rsa.2048.pemProvider Dependent – If you didn’t get a .pem file in with your config files you do not need to add this. If it is you need to ensure the crl.rsa.2048.pem is saved in the /docker/vpn folder
caca /vpn/ca.rsa.2048.crtProvider Dependent – If you didn’t get a .crt file you do not need to add this. If it is you need to ensure the ca.rsa.2048.crt is saved in the /docker/vpn folder

You can now save this file into ‘/docker/vpn’ named ‘vpn.conf’

That’s the VPN settings done, let’s get onto the compose file.

Docker Compose

Next we are going to create a Docker Compose file, this is used to tell Docker how to set up our container with all the variables we require that are not available in the DSM GUI.

Open up Text Editor again and create a new file. Copy and paste the information below into the file.

version: "3.8"
    container_name: vpn
    image: dperson/openvpn-client:latest
      - net_admin # gives docker admin rights to amend network settings
      - /dev/net/tun #points to the tun device created by the syno VPN package
      - /volume1/docker/vpn:/vpn #The location of our config files
      - label:disable
      OPENVPN_OPTS: '--mute-replay-warnings'
      DNS: -- #quad9 DNS this is to help avoid connection issues
    ports: #uncomment ports below for additional applications
#      - 8112:8112 # port for deluge remove the # to use
#      - 9696:9696 # port for prowlarr remove the # to use
      - 8090:8090 # port for qbittorrent
    command: '-f "" -r ""' # amend this in line with your local network settings
    network_mode: synobridge
    restart: unless-stopped

    container_name: qbittorrent
      - WEBUI_PORT=8090
      - /volume1/docker/qbittorrent:/config
      - /volume1/data/torrents:/data/torrents
    network_mode: service:vpn # run on the vpn network
      - vpn
    restart: unless-stopped

You can change the formatting to YAML in the bottom right of the editor to make it easier to read.

We need to make some small amendments to the default settings to ensure they work for you.

ports(optional) If you want to run any other containers through the VPN connection you will need to add their WebUI port numbers to this section. By default we are just passing qBittorrent through. – If you do add something like Prowlarr you will need to move it to this compose file and then set its network mode in line with the one qBittorrent is using. (see the FAQ’s on Page 2)
command(required) in the command section you will see you will need to amend this in line with your local IPv4 settings for your network.
For example if the IP of your NAS is you will use or if your IP is you will use
network_mode (optional) You can see that the qBittorrent container is being told to use the VPN, if you added any other containers such as Prowlarr you will need to change their config in line with this. (See the FAQ’s on Page 2)
PUID(required) The UID you obtained in the user setup guide
PGID(required) The GID you obtained in the user setup guide
TZ(required) Your timezone
If you are having any issues with adding extra containers head over to Discord for some help

You can now save this compose file in /docker/vpn and call it qbittorrentvpn.yml

SSH and Docker-Compose

It’s time to get logged into you Diskstation via SSH, you can do this in the same way as when you obtained your IDs in the ‘Setting up a restricted Docker user‘ guide.

Once you have logged in you will need to give 2 commands, you can copy and paste these one at a time — you will need to enter your password for the command starting with ‘sudo’

First we are going to change directory to where the qbittorrentvpn.yml is located, type the below and then press enter.

cd /volume1/docker/vpn

Then we are going to instruct Docker Compose to read the file we created and complete the set-up of the container. Again type the below and press enter.

sudo docker-compose -f qbittorrentvpn.yml up -d

When the command has completed you should be able to see both qBittorrent and the VPN container running in the list of containers in the Synology GUI.

If you find the VPN container is in a restart loop it means something within the settings is not quite right. Feel free to reach out on Discord or via my contact page (top left of this site), take a look at the VPN container logs and see the FAQ on page 2 for some common issues.

Final steps

As we have used /data/torrents as the mount point for our downloads we need to make sure qBittorrent uses this same file path.

We need to change the file paths by editing the qBittorrent config file, before doing this stop both of the containers.

Go back into DSM and open Text Editor, browse to /docker/qbittorrent/qbittorrent and open the qBittorrent.conf then edit the file in line with the table below, once amended save the changes.

Original ValueNew Value

You can now bring the containers back up again by repeating the steps in the SSH and Docker Compose section above.

Once the containers are running you can log into the Web UI by going to the IP of your NAS followed by port 8090


qBittorrent has a default login of ‘admin’ followed by the password of ‘adminadmin’ you can change this in the settings or remove it altogether if you wish.

Now you are in the UI click on settings cog at the top of the screen, we are going to change one more directory which is the watched folder to /data/torrents/watch. You can also turn on the option ‘keep incomplete torrents in:’ which should already have /data/torrents/incoming’ prefilled.

Next we are going to set a command to run when each torrent finishes to automatically extract any .rar files

Scroll down in the options to the ‘Run external program on torrent completion’ and enter the below, it tells qbittorrent to run unrar and extract the file to the same save path as the original file. This will not delete anything, so you can continue seeding.

unrar x "%D/*.r*" "%D/"

I am not going to walk through all the other settings as you can customise these as you wish.

That’s it you are completely set up!

Something not working – See the FAQs

Throw me some bits or buy me a coffee?

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running the site, you can even buy me a coffee 🙂

Buy Me A Coffee
Doge / Ethereum / Bitcoin

Pages: 1 2

Published inDockerDownload ToolsSynology


  1. Am I able to set up my VPN via Control Panel –> Connectivity –> Network –> Network Interface and skip the VPN set-up described above?

    • Dr_Frankenstein Dr_Frankenstein

      Yes you can, however this will not prevent ip leaks if the vpn connection goes down.

  2. b b

    Would you happen to know how to add other containers to the VPN after everything is set up? I would like to use portainer to add the containers to the VPN. I tried a couple of tutorials online but I can’t seem to get it to work properly.

    • Dr_Frankenstein Dr_Frankenstein

      Hey, see page 2 for the FAQ, it has an example compose with Prowlarr added so you can see how it works.

  3. Manny Black Manny Black

    I’m also getting the vpn always restarting. And the webUI won’t open.

    • Dr_Frankenstein Dr_Frankenstein

      Hey Manny – Can you contact me via Discord or via my contact page on the top left of the site please – It’s easier to fix that way rather than via the comments – Thanks

  4. d d

    Thanks so much for this (and other) useful guides.

    I’m getting this error message. Any troubleshooting suggestions?

    ERROR: for qbittorrent Cannot start service qbittorrent: OCI runtime create failed: container_linux.go:363: creating new parent process caused: container_linux.go:1946: running lstat on namespace path “/proc/26040/ns/net” caused: lstat /proc/26040/ns/net: no such file or directory: unknown

    • Dr_Frankenstein Dr_Frankenstein

      Hey, is your VPN container in a restart loop or has it connected successful?

      • d d

        Thanks for your help here…

        When I first tried it, the vpn connected successfully and stayed connected, but the qbittorrent container threw that error.

        I deleted them both and now when I re-create them, the vpn container is in a restart loop. But the error message is different:

        Cannot start service qbittorrent: Container 95b0156e358e1879adc8054f64b10cd57cd9bcd47ab0db90ae412fb69aa61a41 is restarting, wait until the container is running

        • Dr_Frankenstein Dr_Frankenstein

          OK cool, can you reach out to me either via the contact me page or Discord. The links are in the top left of this site as I will need to check your logs to see why the VPN is not connecting. I suspect it hadn’t actually connected the first time. As without the VPN being up qbittorrent won’t work.

          • d d

            Left this for a while and then came back to it today to try again. After a bit of troubleshooting, here’s what worked:

            In the vpn.conf file, I commented out these lines:

            data-ciphers AES-256-CBC

            data-ciphers-fallback AES-256-CBC

            and added this one:
            cipher AES-128-CBC

            and it seems to be working swimmingly with PrivadoVPN.

            Thanks again for the excellent resource you’ve created here.

          • Dr_Frankenstein Dr_Frankenstein

            D your ears must be burning, a better solution is to delete those two lines from the Privado file as they are redundant and it will work without downgrading the AES strength, I did this about 10 minutes ago on my personal setup..

  5. Dr_Frankenstein Dr_Frankenstein

    I believe it should work, give it a try and let us know.

Leave a Reply

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