qBittorrent 5.2.0 API changes

[buddwm]

Description

As of qBittorrent 5.2.0, the WebAPI now returns HTTP 204 (instead of 200) when a response contains no data (release notes):

WEBAPI: Send 204 when WebAPI response contains no data (Piccirello)

The login response contains no body data, so it now returns 204. However, the qBittorrent widget proxy handler only accepts HTTP 200 as a successful login:

if (status !== 200) {
  logger.error("HTTP %d logging in to qBittorrent.  Data: %s", status, data);
  return res.status(status).end(data);
}

This causes the widget to reject an otherwise successful authentication. The response can be confirmed with curl:

HTTP/1.1 204 OK
set-cookie: QBT_SID_8112=...; HttpOnly; SameSite=Strict

This behavior causes a repeated login error in Homepage logs despite valid credentials:

[2026-05-09T12:59:08.414Z] error:  HTTP 204 logging in to qBittorrent.  Data: 
[2026-05-09T17:45:06.690Z] error:  HTTP 204 logging in to qBittorrent.  Data: 

Expected Behavior

The proxy handler should accept HTTP 204 as a valid login response in addition to 200.

homepage version

latest

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

Reference qbittorrent release logs for changes and confirm with curl.

[shamoon]

Thanks, and thanks for the link. Shouldnt be too bad to handle. Would you be willing to test out a docker image, tagged feature-6650 to verify if the changes work with 5.2.0?

Thanks

[shamoon]

Thanks for testing it out, will be in our next release

#6652

[Reginard]

Tagged feature-6650 solved the issue for me.
Thanks

[buddwm]

Thanks - the feature-6650 tag works for me as well per the include changes in the proxy.js code for handling the 204.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.