@dandylion said in Stalled:
@bi4smooth said in Stalled:
@dandylion said in Stalled:
Hello,
The tracker issues aside, QBittorrent does not behave with our tracker very well because we do not have "Scrape" enabled. I'm going to be honest, I'm not entirely sure what that means, but it was explicitly mentioned in a training document about QBittorrent acting strangely because of it.
Thankfully the fix is easy, if a download is "Stalled", right click it and click "Force Resume". This should resolve the issue 🙂
Thank you,
DandyLion
The qBitTorrent "scrape" issue only comes into play when you complete a download.
"Scraping" is essentially a re-announce to the tracker that you have the complete torrent and are now a seeder, not a leecher.
In qBitTorrent, there is a simple fix: set your client to force re-check upon completion. It will seed properly AFTER the re-check.
I learned something new, Thank you very much, I will update my training materials and pass that information along 🙂
To be completely clear - the part in qBitTorrent about the scrape isn't all there is to a scrape...
Read a full description of a scrape here
But where it comes into play with qBitTorrent is that it "scrapes" at the conclusion of the download - and our tracker doesn't support scrapes - so the qBitTorrent client sits there saying to itself "I'm a seeder" while the GTru tracker says "he's a leecher still"
When you set the force-recheck, and it completes, the qBitTorrent sends a fill ANNOUNCE to the tracker, which is accepted and voila! You're a seeder!
