Qbittorrent users, beware updating now

Apps and Virtualization
1

My apologies if there are existing posts on the subject, but the latest qbittorrent app has problems. Even the update process can break it. So if you are running 1.4.5, aka qbittorrent 5.1.4, don’t update it. Give it some more time to cook, the git forums are busy and they’re squashing bugs already.

Now, if you haven’t installed yet, you will naturally receive this dodgy version if you click install right now. It won’t have the failure to start issue since you didn’t install via update, but you will find a crippling bug where an entire cpu core will peg 100% on idle because of a bug in blank Rss feed handling. During install I believe you can pick a version, so 1.4.5 is OK. With apps it’s the app version and the truenas version; qbit is 5.1.4 and truenas is 1.4.5 but you will see.

Tldr, don’t update to 1.4.6 right now, and new installs should choose 1. 4.5.

1 Like
2

Good heads up.

I’m cautious with major version releases for qBittorrent.

According to the discussion on their GitHub, you can disable RSS to get around this bug. That’s not a solution for those who use the RSS feature, but it can help those who don’t.

3

Working fine in my FreeBSD jail. :smiling_face_with_sunglasses:

4

Or for the hard headed who insist on running 1.4.6/5.2.0 or bsd magicians that like Strongbad I guess. Why work around when 1.4.5 is good to go and they’re about to patch 520 anyway? Thanks for confirming @winnielinnie

5

Hasn’t been pushed to the Docker image yet, thankfully. I’ll probably disable Watchtower just in case.

1 Like
6

Hey folks, I’m coming to this thread after updating to 1.4.6/5.2.0 :roll_eyes:

Anyways, the app now fails to start. It cycles through Deploying/Stopped statuses five times each time I try to start it, and eventually gives up. There’s no other feedback in the web UI about what went wrong, and I can’t access logs in the web UI while it’s failing to start. I also can’t rollback to 1.4.5, because apparently you can’t rollback a stopped app?

Any suggestions for fixing this? Please don’t suggest uninstalling and reinstalling 1.4.5, as my client is seeding 1,000+ torrents, and I really don’t want to have to download them all again :grimacing:

7

Take a look at the app_lifecycle.log

sudo cat /var/log/app_lifecycle.log

The log should give you a reason why the deployment fails

1 Like
8

There’s nothing relating to qBittorrent in /var/log/app_lifecycle.log, and it hasn’t been modified since 24/4/2026 (I updated qBittorent this morning, 11/5/2026)

1 Like
9

Roll back to the previous version until it’s fixed.

10

As per my original post: I can’t roll back, as TN doesn’t allow you to rollback an app that’s not running, and I can’t run it.

11

Fixed it: remove the lockfile from the config folder and it runs.

12

FYI, today’s raft of app updates to v1.4.7 breaks qBittorrent 5.2.0 again. The same solution worked once more for me, though: delete the lockfile in the qBittorrent config directory and start the app.

1 Like
13

Guess it’s time to treat it like npm now, don’t update unless there’s a solid reason.

1 Like