Last updated on 8 January 2025
Important or Recent Updates
Historic Updates | Date |
---|---|
Fresh new guide by popular demand | 28/09/2023 |
Updated with new steps to obtain and change WebUI password | 21/11/2023 |
Issue with passwords has been fixed in 4.6.2 so removed tty line from yaml | 29/11/2023 |
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
- Docker Package, SSD and Memory Recommendations
- Step 1: Directory Setup Guide
- Step 2: Setting up a restricted Docker user
- Step 3: Setting up a Docker Bridge Network (synobridge)
Folder Setup
Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.
/docker/projects/qbit-compose
/docker/qbittorrent
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:
Section | Setting |
---|---|
Project Name: | qbit-project |
Path: | /docker/projects/qbit-compose |
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
services:
qbittorrent:
image: linuxserver/qbittorrent:latest
container_name: qbittorrent
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- WEBUI_PORT=8090
volumes:
- /volume1/docker/qbittorrent:/config
- /volume1/data/torrents:/data/torrents
ports:
- 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.
Variable | Value |
---|---|
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 wikipedia.org/wiki/List_of_tz_database_time_zones |
Ports
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.
Volumes
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 the Synology Firewall enabled please see this additional guide for further info on exceptions and correct set up.
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 by clicking the qbittorrent container select ‘details’ and then view 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 Setup
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.
As we have used /data/torrents as the mount point for our downloads we need to make sure qBittorrent uses this same file path. Open the settings and edit the following paths and save.
Option | Original Value | New Value |
---|---|---|
Default Save Path | /downloads | /data/torrents/completed |
Keep incomplete torrents in | /downloads/incomplete | /data/torrents/incoming |
Monitored Folder (optional) | blank | /data/torrents/watch |
In prior versions of this guide I had a command to unzip RAR and ZIP files, I have removed this as it is not reliable, check out Unpackerr from the menu.
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.
FAQs
Q: I am getting the ‘errored’ status for all my torrents
This is very likely a permissions issue, go to the User and Group guide and see the permission fixes towards the bottom.
Q: Everything seems to be connected but nothing is downloading.
Try grabbing the Ubuntu torrent as that is a sure fire way of testing as generally it has over 3k seeds.
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.
Hi, how do I then connect qbittorrent to Radarr/Sonarr? I am getting a Unable to connect to qBittorrent error. I changed the Port in Radarr/Sonarr to 8090
Hey — it should work either by using the NAS IP and Port OR the ‘synobridge’ gateway IP of 172.20.0.1 and the Port
Hi! Excellent guide!
I would like to add something, as I was stuck for some time.
At the step “Changing the default WebUI login and password”, i couldn’t find the temporary password by going in the “log” section in the UI.
Turns out I needed to click on “container – qbittorrent” and then “Details” from the top menu, and then finally “Log” in the upper hand bar.
Again, thanks, excellent guide.
Thanks for the feedback – I have made the suggested tweak 🙂
Hi, i am getting an error:
File error alert. Torrent: “Crim…N0N”. File: “/data/torrents/incoming/Crim…N0N/Crim…N0N.mkv”. Reason: “Crim…N0N file_stat (/data/torrents/incoming/Crim…N0N/Crim…N0N.mkv) error: Permission denied”
Hi dave – Jump back to the User setup guide – towards the bottom you will find some intructions for fixing permissions
Hello,
So I’m new to this setup, I would like to see if you are able to create a guide for the Tixati torrent? I been using that one more then any other one and I like that torrent much better.
Hey, no immediate plans for Tixati it doesn’t have a native Docker implementation however jlesage has one in his suite of containers.
https://github.com/jlesage/docker-tixati
Feel free to reach out via Discord or my Help Me! Page if you need some steps to set it up.
For the “Firewall Exceptions” section — in the Synology firewall do I need to allow BOTH the WebUI port and the listening port? In other words, for this set-up, do I need to open both 9854 TCP/UDP and 8090, or just 9854?
It will be both – essentially it will depend on what you have opened up already in the firewall – I had to make the section generic as everyones configs could be slightly different, if you already allow all local IPs access it may not be required.