Is there an existing issue for this?
• I have searched the existing open and closed issues
Current Behavior
Bookshelf (hardcover tag) fails to authenticate with qBittorrent 5.2.0 when adding or testing a qBittorrent download client. The error is DownloadClientAuthenticationException: Failed to authenticate with qBittorrent, even though credentials are valid and authentication succeeds via curl from inside the container.
Manual curl from inside the Bookshelf container returns HTTP 204 OK with a valid session cookie, confirming credentials and connectivity are correct. However, Bookshelf treats the 204 as an auth failure.
Sonarr and Radarr (latest linuxserver images) connected to the same qBittorrent instance authenticate successfully. The issue is isolated to Bookshelf.
Expected Behavior:
Bookshelf should accept HTTP 204 as a successful login response from qBittorrent, consistent with the updated API behavior in qBittorrent 5.2.0.
Root Cause:
qBittorrent 5.2.0 changed the /api/v2/auth/login endpoint to return HTTP 204 (no content) on successful authentication instead of HTTP 200 with Ok. in the response body. The upstream Readarr/Sonarr/Radarr codebases have already been patched to handle this (see Sonarr commit ae18ad61bd9865755b4067709de47c1404fd4078 and related PRs), but Bookshelf has not yet incorporated this fix.
Reference:
• qBittorrent issue: qbittorrent/qBittorrent#23270
• Radarr issue: Radarr/Radarr#11339
• Homepage discussion confirming 204 change: gethomepage/homepage#6650
Steps To Reproduce:
1. Run qBittorrent 5.2.0 (linuxserver image rebuilt 2026-05-10 ships this version)
2. Configure Bookshelf (hardcover tag) with valid qBittorrent credentials
3. Click Test on the download client
4. Authentication fails despite valid credentials
Environment
• OS: Ubuntu (Docker, Proxmox VM)
• Bookshelf image: ghcr.io/pennydreadful/bookshelf:hardcover (sha256:388eecc94362580eae31ee0a454be6af516f8a311f8432a521c202fb475f4359)
• qBittorrent: 5.2.0 (lscr.io/linuxserver/qbittorrent:latest)
• Docker Install: yes
• Both containers share network namespace via Gluetun (network_mode: service:gluetun)
Workaround:
Pin qBittorrent to a pre-5.2.0 version until the upstream auth fix is merged into Bookshelf.
Is there an existing issue for this?
• I have searched the existing open and closed issues
Current Behavior
Bookshelf (hardcover tag) fails to authenticate with qBittorrent 5.2.0 when adding or testing a qBittorrent download client. The error is DownloadClientAuthenticationException: Failed to authenticate with qBittorrent, even though credentials are valid and authentication succeeds via curl from inside the container.
Manual curl from inside the Bookshelf container returns HTTP 204 OK with a valid session cookie, confirming credentials and connectivity are correct. However, Bookshelf treats the 204 as an auth failure.
Sonarr and Radarr (latest linuxserver images) connected to the same qBittorrent instance authenticate successfully. The issue is isolated to Bookshelf.
Expected Behavior:
Bookshelf should accept HTTP 204 as a successful login response from qBittorrent, consistent with the updated API behavior in qBittorrent 5.2.0.
Root Cause:
qBittorrent 5.2.0 changed the /api/v2/auth/login endpoint to return HTTP 204 (no content) on successful authentication instead of HTTP 200 with Ok. in the response body. The upstream Readarr/Sonarr/Radarr codebases have already been patched to handle this (see Sonarr commit ae18ad61bd9865755b4067709de47c1404fd4078 and related PRs), but Bookshelf has not yet incorporated this fix.
Reference:
• qBittorrent issue: qbittorrent/qBittorrent#23270
• Radarr issue: Radarr/Radarr#11339
• Homepage discussion confirming 204 change: gethomepage/homepage#6650
Steps To Reproduce:
1. Run qBittorrent 5.2.0 (linuxserver image rebuilt 2026-05-10 ships this version)
2. Configure Bookshelf (hardcover tag) with valid qBittorrent credentials
3. Click Test on the download client
4. Authentication fails despite valid credentials
Environment
• OS: Ubuntu (Docker, Proxmox VM)
• Bookshelf image: ghcr.io/pennydreadful/bookshelf:hardcover (sha256:388eecc94362580eae31ee0a454be6af516f8a311f8432a521c202fb475f4359)
• qBittorrent: 5.2.0 (lscr.io/linuxserver/qbittorrent:latest)
• Docker Install: yes
• Both containers share network namespace via Gluetun (network_mode: service:gluetun)
Workaround:
Pin qBittorrent to a pre-5.2.0 version until the upstream auth fix is merged into Bookshelf.