cross-seed: cross-seed incorrectly thinks torrents already exist in qBittorrent
I’m getting quite a few entries in my log that state as the heading is showing. Basically saying that a cross-seed is available and it exists w/in qbit.
However, when I go to check to make sure I do not find that release with that specific tracker.
Config as follows
// can be either "save" or "inject".
// With "inject" you need to specify the rtorrent rpc url.
action: "inject",
// The url of your qBittorrent webui.
// Only relevant with action: "inject".
// Supply your username and password inside the url like so:
// "http://username:password@localhost:8080"
qbittorrentUrl: "http://<username>:<password>@192.168.1.200:8080",

Not entirely sure why It would be doing that if there isn’t that release from that tracker w/in qbit.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15
This is perfect! Something must be going on with authentication.
The line
means that we’re getting a
403 Forbidden
error from the qBittorrent API. The reason this was showing up as “exists” is because the code was doing roughly the following logic:But that was an erroneous assumption, clearly.
@bobokun are you familiar with this behavior of qBittorrent’s api? Maybe I need to re-authenticate every so often due to session expiration? Or maybe just retry individual requests? I’ll take a look at the Flood codebase.
In https://github.com/mmgoodnow/cross-seed/releases/tag/v2.3.6, I added some logging that will hopefully show what cross-seed sees when it thinks a torrent already exists.
https://github.com/mmgoodnow/cross-seed/blob/d1730f4d0bc09d2a391d66ce8c88c4af966a8265/src/clients/QBittorrent.ts#L84-L99
Hoping to dig into this this weekend.
I haven’t forgotten about this. Just been super busy recently.