Skip to content

qBittorrent in Container Manager on a Synology NAS

Important or Recent Updates
Historic UpdatesDate
Fresh new guide by popular demand28/09/2023
Updated with new steps to obtain and change WebUI password21/11/2023
Issue with passwords has been fixed in 4.6.2 so removed tty line from yaml29/11/2023
Historic Updates

What is qBittorrent?

qBittorrent is a torrent downloader used to both manage torrent downloading and seeding.

If you are looking to combine a VPN with this set up see the GlueTUN guide on the left Menu

Let’s Begin

In this guide I will take you through the steps to get qBittorrent up and running in Docker

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

Folder Setup

Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.


Container Manager

Next we are going to set up a ‘Project’ in Container Manager, a project is used when you want one or more to all be loaded together and uses Docker Compose to do this.

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:

Project Name:qbit-project
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

    image: linuxserver/qbittorrent:latest
    container_name: qbittorrent
      - PGID=65432 #CHANGE_TO_YOUR_GID
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
      - WEBUI_PORT=8090
      - /volume1/docker/qbittorrent:/config
      - /volume1/data/torrents:/data/torrents
      - 9854:9854/tcp # Forwarded Port on Router TCP
      - 9854:9854/udp # Forwarded Port on Router TCP
      - 8090:8090/tcp # port for qbittorrent webui
    network_mode: synobridge
    restart: always

Environment Variables

We are now going to amend some key variables to make sure the container has access to our folders and also knows where we are in the world. Don’t change any other settings other than those I mention.

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


Nothing to change here, the webui will run on port 8090 and the ports we will be using for the torrent protocol will be 9854 for TCP and UDP.


By default, I have assumed you have your config files stored on /volume1 if these are located on another volume amend this line accordingly.

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 images will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.

You will now see your qbit-project running with a green status on the left-hand side.

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.

Changing the default WebUI login and password

If you skip this step you won’t be able to log in.

Now the container has started open it in the Docker UI and go to the Log tab. Within the logs you will see the login details

Now before doing any more of the guide go to the Web UI by going to the IP of your NAS followed by port 8090 and log in. Then on the WebUI tab change the defaults to your own and save them.

Now continue on..

Router Port Forwarding

As you can imagine there are thousands of possible router configs out there, so you will need to check the manual for your own.

Essentially you need to Port Forward port 9854 TCP and UDP to your NAS IP address. This will make you connectable for all peers. Most routers support UPnP or NAT-PNP which will automatically set up ports however it’s usually more secure to turn these off and do it manually.

Final qBittorrent 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. Do this by selecting the Project from the main UI and under Action selecting ‘Stop’.

You can edit this file in a number of ways, but to keep the guide OS-agnostic we will be using the Synology Text Editor package which can be installed via Package Center.

Open Text Editor and 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 starting the Project.

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


Log in with the username and password you created earlier.

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 (Note if you have any issues with this I would recommend using Unpackerr the guide is on the menu)

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/"

Connection Settings

The last step is to tell qBittorrent to use the correct port for communication enter 9854 in the Listening Port.

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

That’s it.


More will be added as questions come up

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.

Published inDockerDownload Tools 7.2Synology


  1. Kidego Kidego

    Appreciate your work but i’m getting the following error…

    Error response from daemon: Bind mount failed ‘/volume1/data/torrents’ d
    exit code: 1

    • Dr_Frankenstein Dr_Frankenstein

      Double check you folders naming and they are all lowercase and are on volume1

  2. Scoreburn Scoreburn

    Are there any risks associated with the configuration of port 9854 as shown in the final step? Does it need to be forwarded on my router? Do I have to secure that port via VPN in any fashion with gluetun in the yml file?

    Thank you in advance! Everything has been working magnificently thus far and its all thanks to your guide!

    • Dr_Frankenstein Dr_Frankenstein

      Hey, so if you are using GlueTUN you should NOT be port forwarding anything on the Router side as this will run the risk of exposing qbit to your local WAN rather than via the VPN. If however you are using no VPN then you will need to open the port in order to be connectable via other torrent clients. Keep in mind that you need to make sure whatever you are uploading is legal where you live.

      • Scoreburn Scoreburn

        Hey thanks so much for your response. This clears things up for me and supplements some reading I’ve been doing since my initial post.

        I did have another question that you may or may not be able to help with. I followed your guide for setup of qBit and gluetun, however, the upload/download speeds on qBit are extremely poor. I’ve tried the same downloads via my desktop version of qBit and they go much faster.

        I ran some speed tests on the Synology NAS (DS1522+) itself, qBit container, and gluetun container. Here are the results of my speed tests:

        The NAS itself:
        Download = 934.29 Mbps
        Upload = 103.92 Mbps

        qBittorrent Container:
        Download = 0.79 Mbit/s
        Upload = 2.72 Mbit/s

        gluetun Container:
        Download = 21.38 Mbit/s
        Upload = 52.70 Mbit/s

        Any idea why qBit might be demonstrating such poor performance? Anything helps. I just simply don’t know where to go about solving this issue and whether or not it is solvable or just the nature of the setup.

        • Dr_Frankenstein Dr_Frankenstein

          From a VPN perspective the closer the server the better, however you seem to be getting some pretty poor performance off the VPN as well which points at some issue with Docker.

          I would initially try a very close server to you, just to see if that helps with GlueTUN itself. Also, might be worth doing a reboot to make sure the Docker network has set up correctly. You are doing the right testing (spotted you on Reddit)

  3. Bfizzle Bfizzle

    Your guides have been a blessing, as I’ve progressed a lot farther than a year or so ago when I first tried to setup qBittorrent.
    Here is where I am getting stuck though. Instead of using sonarr, I am trying (because it’s what I know) to setup RSS Downloader to automatically download files and place them in their destined folder outside of /data. The folders are still on volume1, but instead scattered elsewhere on my NAS.

    If I try to have RSS downloader automatically move those files there, they get stuck in the incoming folder upon completion. I can’t figure out the fix to this, as I’ve given dockerlimited and dockergroup read/write permissions to these folders. Is there somewhere else I need to give permission to outside of those user and groups? Anything glaring I would be overlooking to automatically move files outside of /data?

    • Dr_Frankenstein Dr_Frankenstein

      Oh hey, so this is an easy fix. In the guide we use the /data/torrents mount point so qbit cannot see outside of this.. adjust the yaml volumes section.

      – /volume1/data:/data

      This will allow qbit access to folders outside of the torrents folder.

      You can add additional mount point if you wish for example as share called ‘othershare’ on volume1

      – /volume1/othershare:/othershare

      • Drez143 Drez143

        You are amazing, thank you! I would have never realized that piece, as I kept rebuilding and retracing the steps but overlooked that simple piece.

  4. bro708 bro708

    Followed this but all downloads stay in the incoming directory, not moved on completion and if I try to move them manually QBT gives the message “Cannot make save path”. Any ideas?

    • Dr_Frankenstein Dr_Frankenstein

      I would double-check the permissions for the completed folder, might be worth deleting it and recreating. Failing that jump back to the User and Group guide and check the permission fix towards the bottom.

  5. After the installation I am getting an error:
    Container qbittorrent Starting
    Error response from daemon: network synobridge not found

    • Dr_Frankenstein Dr_Frankenstein

      You skipped a step at the start of the guide to create the user defined bridge.

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. – writing Synology Docker Guides since 2016 – Join My Discord!