Skip to content

support for qbit 5.2 #1259

Description

@notifiarr-bot

Hi, sorry if this is already known, I searched Discord for “204” but didn’t find anything obvious.

Notifiarr client seems to fail qBittorrent authentication with qBittorrent v5.2.0.

qBittorrent WebAPI login now returns:

HTTP 204 OK
Set-Cookie: QBT_SID_13782=...

Notifiarr reports:

authentication failed: 204 OK

Credentials are valid. I confirmed with curl that login succeeds and the cookie is returned. I also tested a temporary reverse proxy workaround that converts HTTP 204 to HTTP 200 Ok. and duplicates QBT_SID_13782 as SID, and Notifiarr works again.

It looks like Notifiarr may still expect the old qBittorrent behavior: HTTP 200 + SID cookie, while qBittorrent 5.2.0 now uses HTTP 204 and QBT_SID_.

Could you confirm if support for qBittorrent 5.2.0 WebAPI auth changes is planned or already tracked somewhere?


qBittorrent 5.2.0 changelog mentions:
- WEBAPI: Send 204 when WebAPI response contains no data
- WEBAPI: Append port to session cookie name

https://github.com/qbittorrent/qBittorrent/blob/master/Changelog

Origin user: bertrand
Origin message: Discord Server Link
Reporting user: twitchcaptain
Reporting message: Discord Server Link

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions