May 10May 10 13 hours ago, jolma said:This also happens to me, I cant log in, says connection refused too. Please help.23 hours ago, Koenig said:+1, Accessed the GUI some week ago, bout no luck today, just says "connection refused"...Found the solution:1. Stop the qbittorrent docker2. go to mnt/user/app data, rename the qbittorrent (as a backup, name it whatever you like).3 start the qbittorrent docker (this will like a new bittorrent, set a new user detail (login/password))4. stop the qbittorrent docker again (create path download exactly as before if you installed a new qbitorrent)5. copy BT_Backup, categories.json & qbittorrent.conf from backup to new qbittorrent.6. start qbittorent docker, it will be the same but new client. Edited May 10May 10 by jolma add detail
May 10May 10 Hello All;This isn't adding any great substance to the discussion but for information purposes, I am running 5.2.0 (linuxserver.io's version). It looks like it was auto-updated on May 7.I've restarted the container, refreshed the web ui, logged-out and back in. All appears to be working.I am running UnRaid OS Pro v7.2.3.Here is the tail of the container's log:───────────────────────────────────────Linuxserver.io version: 5.2.0_v2.0.12-ls454Build-date: 2026-05-07T08:42:43+00:00───────────────────────────────────────[custom-init] No custom files found, skipping...WebUI will be started shortly after internal preparations. Please wait...******** Information ********To control qBittorrent, access the WebUI at: http://localhost:8080[ls.io-init] done.
May 10May 10 Latest issue with the webui not starting can be fixed here:https://github.com/linuxserver/docker-qbittorrent/issues/432 It was an upstream issue. Edited May 10May 10 by Einsteinjr
May 11May 11 17 hours ago, Einsteinjr said:Latest issue with the webui not starting can be fixed here:https://github.com/linuxserver/docker-qbittorrent/issues/432It was an upstream issue.Thank you!I can confirm removing the lockfile gets the WebUI on 5.2 to load. Edited May 11May 11 by Koenig
May 11May 11 Confirm too.The "problem" is that it happened twice in two days.(no gui, delete file, fixed, no gui next day, delete file, fixed)I hope the forgotten lockfile eventually IS deleted when updating the container.BTW, I remember the same issue a few years ago (!) in same container.
May 12May 12 Man the internet is always there for me. I upgraded all the containers and after a while when opening qbittorrent i was getting basically nada, i though it might be a problem with the reverse proxy, but the other containers were working fine. Maybe something in the filesystem got messed up? rebooted unraid, nada. Oh, i remember seeing a new update for qbittorrent on reddit, maybe it was a bad update? lets look up unraid forums. And here it is, you guys with the same problem and how to fix it. I love the community. I have pinned version 5.1.4 for the moment anyways. I'll wait a bit as @NLS is saying it might happen again even after deleting the file.
May 14May 14 On 5/11/2026 at 12:15 AM, Einsteinjr said:Latest issue with the webui not starting can be fixed here:https://github.com/linuxserver/docker-qbittorrent/issues/432It was an upstream issue.thanks so much ! This fixed it for me!
May 15May 15 On 5/10/2026 at 7:15 PM, Einsteinjr said:Latest issue with the webui not starting can be fixed here:https://github.com/linuxserver/docker-qbittorrent/issues/432It was an upstream issue.it'd be great if they actually fixed itthis has happened repeatedly 3 times now
May 19May 19 ...yeah happened to me again. Seems with every update we need to manually delete that file (can that not be done with some startup script or smth?)...And as I said I remember this years back happening again.
June 2Jun 2 Has there been a solution for changing the torrent port? Regardless of how I configure, the container port is fixed to 6881. If I set the client to the same port, I show as unfirewalled however 6881 is blacklisted on several trackers. If I set to another, forwarded port, I show as firewalled and cannot connect to passive peers.edit: as humbling as it is to come back and add this, I haven't seen it mentioned before but all you need to do is remove and replace the existing TCP and UDP port mappings Edited June 2Jun 2 by airtower just a fool
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.