Skip to content
Discussion options

You must be logged in to vote

This was generated by AI during triage.

This is a bug in qBittorrent, not qui. qBittorrent's /api/v2/sync/maindata endpoint dropped queued torrent field updates when a client repeated a request with an older response ID. Clients like qui then kept stale progress values while newer state values came through. That matches the stuck 99.x% and wrong status reported here and in #2389.

Upstream tracked it in qbittorrent/qBittorrent#24845. qbittorrent/qBittorrent#24875 closed it as completed. Update qBittorrent to a release that includes that fix. Until then, restarting qui or disabling and re-enabling the instance forces a full sync and clears the stale values.

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by milkers69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on docker torrent sse external-bug
3 participants