-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A private torrent suddently becomes a public torrent #20743
Comments
Are you sure you are describing the issue correctly? One and the same torrent cannot be private and public, only if it is two different torrents (with different hash). |
The workaround I used was to download the torrent file again and add it to qBittorent. Despite getting an error in the log:
The torrent magically becomes private torrent again (DHT/PeX/LSD disabled with a "this torrent is private" message). |
It suddenly became public from what I can tell (using the DHT/PeX/LSD message). Unfortunately due to #14771 I can't be 100% sure. And the libtorrent code doesn't lie, it indeed uses the special |
And given the workaround I tried (used the workaround twice and fairly certain it does work), the "public" torrent in the queue and the private torrent file I downloaded again should have the same hash (or I won't see the log line). |
Perhaps the torrent is hybrid and that plays a role too. |
Oh there's another symptom that I suspect is relevant. When this happened to one of my torrents today, I was trying to confirm if the torrent file contains the "private" bit. But looking at the After I tried the workaround of downloading and importing the torrent file, I now can find the This is potentially relevant because |
A .torrent file cannot disappear by itself. In any case, need steps to reproduce the issue. |
qBittorrent & operating system versions
qBittorrent: 4.6.4 x64
OS: Synology DSM 7 (run qBittorrent in Docker)
Qt: 6.6.2
Libtorrent: 2.0.10.0
What is the problem?
Sorry if the title is a bit confusing.
I use qBittorrent to download content from private trackers exclusively, all my torrent files should be private torrents.
I've seen at least 3 times when a torrent finishes 99% and suddenly it stuck at "Fetching Metadata" (or something similar, sorry I forgot the exact words). For some PT site, I even got a tracker error message "Banned client".
I've been confused by this behavior for a long time and finally noticed one of the PT site showed the user agent I used was
curl/7.81.0
, which led me to https://github.com/arvidn/libtorrent/blob/8a7aa8311387b8d530a2ec2a3eb5974fec5edb64/src/http_tracker_connection.cpp#L247-L249.Reading the libtorrent code around it, it seems like the
curl/7.81.0
user-agent is only used when anonymous mode is enabled (I did enable it), and the torrent is a public torrent (this should NOT be the case!). And when I check the torrent, sure enough I don't see DHT/PeX/LSD disabled with a "this torrent is private" message!Since I was able to download the torrent to 99% w/o get banned message, the torrent must initially a private torrent when added to qBittorrent, and suddenly becomes a public torrent at a later time.
I grabbed the
$HASH.fastresume
file and it indeed showdisable_{dht,lsd,pex}: 0
:Steps to reproduce
I don't know how to reproduce this issue, this seem to happen spontaneously when a torrent is almost finished download.
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: