8 hours ago, uCoreX said:

Found this on the qbittorrent forum:

Close qbitt. and edit qbittorrent.ini file.

Under [BitTorrent] section, add a new line:
 

Session\TorrentContentRemoveOption=Delete

 

would this make the default behavior for removing torrents also delete the files? what if i want to remove torrents without deleting files

12 hours ago, Linguafoeda said:

would this make the default behavior for removing torrents also delete the files? what if i want to remove torrents without deleting files

 

Quote

what if i want to remove torrents without deleting files?

yes you can remove torrent without delete the file.

Edited October 20, 20241 yr by uCoreX

I ended up not doing the fix noted above in config but looks like my qbit container is back to normal being able to delete files

whats the easiest way to restart if my VPN autoupdates? i tried using 'autoheal' but that caused my system instability (unraid would lock up and not be reachable). 

 

Is there a way to autorestart when the VPN container restarts?

The webUI is stuck when thousand of torrent added, for example add torrent dialog or select status, how can i improve?

Edited November 24, 20241 yr by hodge.shen

On 10/2/2022 at 11:05 PM, Shivam Amin said:

For context, when I set network mode to bridge, remove the --net=container parameter, I can access the ui but it's not behind a vpn. I would like to avoid having qbit use port 8080

@Shivam Amin Did you ever find a solution?

I'd also like to avoid running qbit in bridge mode while it's webui port is configured!

Is it possible to set Qbittorent to move completed torrent that have a "state" of Done. I set my torrents to stop seeding once they hit a ratio of 1.0. I'd like to set qbittorent to move the files once they are done seeding.

After last update (?), my container shows empty.
Although it shows that I have 501 torrents (most seeding).

What's up???

Edited May 5, 20251 yr by NLS

23 hours ago, NLS said:

After last update (?), my container shows empty.
Although it shows that I have 501 torrents (most seeding).

What's up???

...and since nobody gave any feedback (which is a bit sad), I have to say I fixed it by clearing cookies for the address.

On 5/6/2025 at 7:47 PM, NLS said:

...and since nobody gave any feedback (which is a bit sad), I have to say I fixed it by clearing cookies for the address.

Thanks! Qbit has been a bit slow lately, context menus are slow to load.

Hi Folks!

Getting some errors on trackers after I updated to 5.1

The error on the trackers show: host not found (non authorizative) try again later

Note all trackers worked fine with prior versions.

Someone shared this error report: https://github.com/qbittorrent/qBittorrent/issues/22366

But how does this work with the Docker version for Unraid? Can this be fixed?

Note that not all trackers fail, just a few.

A little worried... Woke up today and my server was unresponsive. Possibly overheated in this british heatwave.

I restarted the server and all seemed well. I started my *arrs and grabbed a couple torrents I'd missed yesterday/today.

So I started Qbittorrent and opened the WebUI, but when it loaded, every single torrent is now at 0.0% and "downloading metadata" which I've never seen before. They were doing this all at once as I don't use queuing. The vast majority have been renamed to their hash, it seems, so I can't tell from a glance what they are.

I restarted the container to no avail. I noticed that a handful were "downloading" not just "downloading metadata", so I implemented the queue. A load are Checking and it's probably going to overheat the server...

Is this just a waiting game while the system resets or something? Or should I shut qbt down or something?

Thanks

Hey all, I'm receiving terrible download performance with this container (and binhex qbit, transmission and deluge). I've troubleshooted disk and network performance and I've been unable to find a solution. Downloads are going to a cache (2x 990 pros).

Speeds will start at 125+mb/s then quickly drop to 50mb/s within 10 seconds. And over the course of a minute(ish) will fall to <10mb/s where they will stay. Has anyone had this? It happens with all my p2p containers, regardless of which one I use.

More details in my original unraid support thread here: https://forums.unraid.net/topic/192864-poor-download-performance/

Hello,
Suddenly Qbittorrent won't allow login. No matter what.
I tried:
- the default adminadmin
- the password generated in the internal log
- the reset password hack (WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)" that you can add to the config file
- deleting the whole docker, directories, etc.... and reinstalling from scratch
- even tried other versions of Qbittorrent dockers available

Nothing helps. I am stuck at the login page.
BTW, at the same time Qbittorrent stopped working in bridge mode. It does work in host mode. But no login.
Please help. (Transmission and Deluge are no match)

Solved it using AI: Bypass Authentication (Whitelist) added to conf file manually

Edited February 27Feb 27 by xtrips

On 2/27/2026 at 9:06 PM, xtrips said:

Hello,
Suddenly Qbittorrent won't allow login. No matter what

I've had the same problem. For me it doesn't work when I go to the Unraid UI, select qBittorrent and press WebUI. But if I just enter the IP/port manually it accepts the login.

What is wrong with this container these last few months? After every update almost I have to struggle with the conf file, fiddling with it so that I can log back in. Every time there is an update it's a pain.

I use this for years. Today although the container "works" (?), I don't have any gui!

Any ideas?

On 5/8/2026 at 10:48 AM, NLS said:

I use this for years. Today although the container "works" (?), I don't have any gui!

Any ideas?

+1, I have the same issue. Container log doesn't show any error.

On 5/8/2026 at 10:48 AM, NLS said:

I use this for years. Today although the container "works" (?), I don't have any gui!

Any ideas?

+1, Accessed the GUI some week ago, bout no luck today, just says "connection refused"...

Quick correction to my previous post: this turned out to be a false alarm on my end, qBittorrent 5.2.0 works fine. It started with Electorrent failing to connect after the upgrade (which just needed its own update to support 5.2), then I tried opening the WebUI from the Unraid Docker template and it didn't load either, which made me think the upgrade broke the WebUI. Turns out the template was pointing to the wrong port (8080) while the actual WebUI is on 8085. With the correct port the WebUI works fine, and Electorrent is also working again after its update. Sorry for the noise.

Help!

I was trying to roll back my version, and must have messed up what I put in for the repository and now my qBt docker is gone.

I'm not docker savy enough to know how to find/fix this. Could someone please help me or point me in the right direction?

Thank you!

1 hour ago, Southpaw32 said:

Help!

I was trying to roll back my version, and must have messed up what I put in for the repository and now my qBt docker is gone.

I'm not docker savy enough to know how to find/fix this. Could someone please help me or point me in the right direction?

Thank you!

Ok, so I did the "Previous Version" in the Apps section and I'm up and running again. Whew.

10 hours ago, Koenig said:

+1, Accessed the GUI some week ago, bout no luck today, just says "connection refused"...

This also happens to me, I cant log in, says connection refused too. Please help.

I tried to roll back to 4.6 but the the docker disappeared, after that I reinstalled it from "Apps" but I can still not get to the UI and now it seems all my torrents are gone, the sites says I'm seeding 0 torrents, this was not the case before, what do I do now? (I seeded 600+ torrents, that'll be much work adding back...)

I managed to roll back to 5.1.4 + I found a month old appdata-backup, this got me into the UI again, there must be issues with 5.2.

In 5.1.4 the log for the docker says "WebUI will be started shortly after internal preparations. Please wait..." and then "To control qBittorrent, access the WebUI at: http://localhost:8080", neither of these lines appears in the 5.2 log, so to me it seems the 5.2 docker never starts the WebUI....