From 0c0c7dc6b32b46e813a8441c041f1b30658b9154 Mon Sep 17 00:00:00 2001 From: Roxedus Date: Thu, 30 Nov 2023 10:45:42 +0100 Subject: [PATCH] Resolve Qbittorrent --- content/issues/2023-11-22-qbittorrent.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/issues/2023-11-22-qbittorrent.md b/content/issues/2023-11-22-qbittorrent.md index 105948a2..76151281 100644 --- a/content/issues/2023-11-22-qbittorrent.md +++ b/content/issues/2023-11-22-qbittorrent.md @@ -2,12 +2,16 @@ title: 'Known Issue: qBittorrent 4.6.1 Web UI Password' date: '2023-11-22 18:00:00Z' severity: notice -resolved: false +resolved: true +resolvedWhen: '2023-11-30' affected: - 'Known Issues' - 'qbittorrent' section: 'issue' --- + +**Fix has been released, update to 4.6.2. The [readme](https://github.com/linuxserver/docker-qbittorrent#application-setup) has been updated to reflect how the password for new installs are handled going forward** + There is a known issue with qBittorrent 4.6.1, due to an [upstream change](https://www.qbittorrent.org/news#mon-nov-20th-2023---qbittorrent-v4.6.1-release) which changes the Web UI password to a random value on startup if you have not changed it from the default. This change has been made for security reasons due to hackers exploiting users who have exposed their instances to the internet with default credentials. Due to an [upstream bug](https://github.com/qbittorrent/qBittorrent/issues/19984) the generated password is not printed to the container logs, making it impossible to log in.