Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] Linuxserver.io - Qbittorrent

Featured Replies

7 minutes ago, marcow said:

Same issue for me since the update

rollback to previous and set own password in UI and then update again

  • Replies 484
  • Views 276.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Are you changing it in the Qbt WEBUI settings or the container?   Edit: I found I had the same issue as you, but was able to figure it out. With the base settings, any time you change the po

  • Again as per the readme, it states `need to change both sides` aka the container port and host port to match and you haven't done this.

  • Basically install unrar via the nerdpack plugin, then run command on completion:   unrar x "%F/*.r*" "%F/"  

Posted Images

The why & what to do 

 

2 hours ago, kitllama said:

The why & what to do 

 

 

Hmmm, maybe I'll try that again. It didn't work yesterday when I tried it. Although I have binhex-deluge up and working, so there's not much motivation. Especially after reading through this thread and seeing the same issue being asked about for FOUR years.

 

Thanks.

I'm having the same issue with the password having not been set previously, and now even though i can see in the log what the password is, it will not accept it.

 

So I'd like to roll back, but i can't find how to do it in a lcear way... i have looked in "Previous Apps" and that deosn't help, and other post I have seen about rolling back dockers refer to opening the Dockers hub and changing tags, but I can't find this.

 

Can someone explain simply how to rollback qbittorrent to the previous version where I can set a password?

 

Thank you, using this tip I was able to roll back and to log in on WebUI

How do I go about port forwarding qbittorrent on UNRAID with my router?  I know how to port forward to my computer but I don't think I am doing it right for qbittorrent on UNRAID.  My download and upload speeds for some torrents are really slow and I believe this to be the issue.  Or is there any way for me to check on UNRAID that my ports are being blocked?  Thanks.

  • 2 weeks later...
On 7/19/2023 at 10:55 PM, pranasziaukas said:

How do I change the Docker port 6881? It's not adjustable in the template for some reason, and no matter what I do I get

```

docker run
  -d
  --name='qbittorrent'
...
  -p '8080:8080/tcp'
  -p '54321:6881/tcp'
  -p '54321:6881/udp'

...

```

which drives me crazy.

 

I can port forward whatever in my router but, to the best of my understanding, the qBittorrent client reports its port 6881 to a torrent tracker which blacklists 6881.

 

create a docker network in shell first and switch from Host to your created network

 

open shell:

docker network create yourawesomenetwork

 

  • 1 month later...

I'm not sure if anyone else has come across this issue, but I've been having some pretty severe memory leak issues with the linuxserver qbittorrent docker container recently.  I transferred ~10,000 torrents (50TB total) and fast resume data from another server and split it across two separate lscr qbit instances (roughly 5k torrents each).  The files themselves are stored on an 8-wide raidz2 pool dedicated for torrents.  Both instances are just seeding (no downloading).  And no matter what I try, the qbit container eats up more and more RAM until it almost locks up the server. 

 

I have 128GB RAM (64GB for ZFS + 64GB for everything else) and qbit will easily eat up 40GB of RAM before I have to kill it.  This happens with every version of qbit I've tried: 4.3.9, 4.4.5, 4.6.0, 4.6.2.  I've tried both libtorrent v1 and v2 with all of these builds as well.  Nothing works.  I can limit RAM to 8G or 16G via docker compose, but that makes the container endlessly reset itself when it runs out of RAM.  This causes the appearance of phantom torrents with the tracker and wildly fluctuating ul/dl speeds.

 

Strangely enough, I have another active lscr qbit container (latest repo -- 4.6.2) with around 6,500 active seeding torrents in it and that container only uses around 3GB of RAM.  This is all on the same unraid server.  

 

I tried the binhex container and same issue.  As a last resort, I spun up a new hotio qbit container running 4.6.2 (libtorrent v1) and put the original 5k torrents into it.  It's been pretty stable so far, only using 4GB RAM at present.  

 

I'm not sure what the problem is, but I've never run across such memory leaks across so many different versions of qbit.  Any suggestions would be greatly appreciated.

 

  

10 hours ago, dyno said:

I'm not sure if anyone else has come across this issue, but I've been having some pretty severe memory leak issues with the linuxserver qbittorrent docker container recently.  I transferred ~10,000 torrents (50TB total) and fast resume data from another server and split it across two separate lscr qbit instances (roughly 5k torrents each).  The files themselves are stored on an 8-wide raidz2 pool dedicated for torrents.  Both instances are just seeding (no downloading).  And no matter what I try, the qbit container eats up more and more RAM until it almost locks up the server. 

 

I have 128GB RAM (64GB for ZFS + 64GB for everything else) and qbit will easily eat up 40GB of RAM before I have to kill it.  This happens with every version of qbit I've tried: 4.3.9, 4.4.5, 4.6.0, 4.6.2.  I've tried both libtorrent v1 and v2 with all of these builds as well.  Nothing works.  I can limit RAM to 8G or 16G via docker compose, but that makes the container endlessly reset itself when it runs out of RAM.  This causes the appearance of phantom torrents with the tracker and wildly fluctuating ul/dl speeds.

 

Strangely enough, I have another active lscr qbit container (latest repo -- 4.6.2) with around 6,500 active seeding torrents in it and that container only uses around 3GB of RAM.  This is all on the same unraid server.  

 

I tried the binhex container and same issue.  As a last resort, I spun up a new hotio qbit container running 4.6.2 (libtorrent v1) and put the original 5k torrents into it.  It's been pretty stable so far, only using 4GB RAM at present.  

 

I'm not sure what the problem is, but I've never run across such memory leaks across so many different versions of qbit.  Any suggestions would be greatly appreciated.

 

  

 

@dyno I am having the same problem with much less torrents (136). I set a container limit on the RAM and it slowly crawls up to 100% and resets. This happens constantly

  • 1 month later...

I've encountered the following issue:

In chrome, the file lists on the right side are not visible any more. The issue is recent (march 2024). I'm not sure when exactly it appeared, but it must have happened with a recent Chrome update (122.0.6261.129 (Offizieller Build) (64-Bit) (cohort: Stable) ) (Windows 10). I've tested other browsers (Edge, Opera, Firefox) and the list works fine there.

In detail:

the right side file lists are just blank, the columns are there, but no items. (while they are there in other browsers). No visible script errors, no ad-blockers active. It worked fine for years before, and I didn't change or update anything, well, except Chrome itself. 

It works just fine on Chrome 109 and any other browser I've tried,  that's why I'm thinking it must be related to a change in Chrome.

Has anyone else encountered the issue?

Default settings for UID, GUID and umask in the docker template are: 99, 100. 022

These produce folder with drwxr-xr-x  and files with -rw-r--r-- permissions.

How to setup these variables correctly to much Unraid default permissions so drwxrwxrwx for directories and for files -rw-rw-rw-

 

Can maintainer fix the template to match the default Unraid permissions?

  • 2 weeks later...

Is anybody else having the good old desktop qbittorrent issue where the "Completed on" tab sorts recently downloaded files on top but hides currently downloading files at the bottom of the list?... I've been trying to find information on this topic online with no luck.

  • 6 months later...

Uhh my qBittorrent is in dark mode now starting today, how do I get it back to normal?

in the process of trying to migrate to a better-organised system from a manually managed system that I've had for years, I've got a new instance of radarr and I want the download location set in radarr when adding to be replicated as the default location in qbt.

 

i used to have a manually-set destination as it was the most-used, but i had to manually change for thousands of movies. it wasn't so much of an issue, but i did always lament having to do it, so i want it to be automatic.

 

however, now i removed anything in the "default download location" field in settings, but it resorts to "/config/Downloads" and I don't quite know why - can anyone tell me? a quick 10 second fix, i'm sure.

  

On 10/1/2024 at 10:07 PM, nxtiak said:

Uhh my qBittorrent is in dark mode now starting today, how do I get it back to normal?

 

I'd also like to know how to change back to light mode.

 

Also - I'm noticing that files aren't being deleted even though i select the checkbox "Also remove the content files". Anyone know what could be causing this, some sort of permission issue with qbit container not being able to delete files it's creating?

Edited by Linguafoeda

Hi all,

 

As I didn't find any solution in this threat I am sure that I am doing something wrong:

 

I want to change port 6881 to some other port. I thought I just edit the three entries in the template ("Port: 6881:" for TCP "Port: 6881:" for UDP and "TORRENTING_PORT:"). So I changed the value 6881 for all three entries to "22000" and of course I changed the port-forwording in my router accordingly. However the port is still not reachable. It works perfectly with the default settings but it looks to me as if the change won't have any effect.

 

I tested multiple different ports but it only seems to work with the default port of 6881.

 

Btw: I left the WebUI on 8080 but the behaviour is the same there... any change to the default doesn't seem to have an impact.

 

What am I overseeing here?

 

Thanks for your support.

 

quicky

Edited by quicky

On 10/11/2024 at 11:16 PM, Linguafoeda said:

  

 

I'd also like to know how to change back to light mode.

 

Also - I'm noticing that files aren't being deleted even though i select the checkbox "Also remove the content files". Anyone know what could be causing this, some sort of permission issue with qbit container not being able to delete files it's creating?

 

bump

On 7/19/2022 at 2:06 PM, gaikokujinkyofusho said:

For some reason I cant seem to access the webgui, everytime I try to I get:

 

Unable to connect

Firefox can’t establish a connection to the server at localhost:8082.

 

have tried using my lan ip 192.168...:8082

same error.

 

I figured I might be asked about logs and settings so:
 

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service 00-legacy: starting
s6-rc: info: service 00-legacy successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/01-envfile
cont-init: info: /etc/cont-init.d/01-envfile exited 0
cont-init: info: running /etc/cont-init.d/01-migrations
cont-init: info: /etc/cont-init.d/01-migrations exited 0
cont-init: info: running /etc/cont-init.d/02-tamper-check
cont-init: info: /etc/cont-init.d/02-tamper-check exited 0
cont-init: info: running /etc/cont-init.d/10-adduser
cont-init: info: /etc/cont-init.d/10-adduser exited 0
cont-init: info: running /etc/cont-init.d/30-config
cont-init: info: /etc/cont-init.d/30-config exited 0
cont-init: info: running /etc/cont-init.d/90-custom-folders
cont-init: info: /etc/cont-init.d/90-custom-folders exited 0
cont-init: info: running /etc/cont-init.d/99-custom-files
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun qbittorrent (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
s6-rc: info: service 99-ci-service-check successfully started
[migrations] started
[migrations] no migrations found

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    99
User gid:    100
-------------------------------------

[custom-init] no custom files found exiting...
[ls.io-init] done.

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8082

 

screen shot of settings attached.

Screenshot 2022-07-19 at 13-26-58 Tower UpdateContainer.png

I am having this issue on 5.0 as well.  Worked fine before.

 

On 10/11/2024 at 11:16 PM, Linguafoeda said:

  

 

I'd also like to know how to change back to light mode.

 

Also - I'm noticing that files aren't being deleted even though i select the checkbox "Also remove the content files". Anyone know what could be causing this, some sort of permission issue with qbit container not being able to delete files it's creating?

 

I'm having an issue where qbittorrent won't delete files even though i select "also remove the content files". Anyone know what could be causing this, some sort of permission issue with qbit container not being able to delete files it's creating?

10 minutes ago, Linguafoeda said:

 

 

I'm having an issue where qbittorrent won't delete files even though i select "also remove the content files". Anyone know what could be causing this, some sort of permission issue with qbit container not being able to delete files it's creating?

I am also having this issue.

4 hours ago, sittingmongoose said:

I am also having this issue.

Found this on the qbittorrent forum:

Close qbitt. and edit qbittorrent.ini file.

Under [BitTorrent] section, add a new line:
 

Session\TorrentContentRemoveOption=Delete

 

Edited by uCoreX

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.