-
-
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
Problems with converting non-I2P torrent to I2P torrent #19759
Comments
I've noticed that removing the trackers from a clearnet torrent doesn't always remove ALL of them. It may appear like it has in the trackers tab, but exporting the .torrent file and opening it in a tool like Torrent File Editor ends up showing clearnet trackers. Using said tool to remove all of the trackers and only adding i2p and saving the torrent will work. |
@Vort |
If I remember correctly, libtorrent allows clients to change I2P status of torrent.
I2P status is detected correctly after client restart. Another hack is to add torrents with manually edited magnet links. By the way, |
@Vort |
I've also encountered this. You can close qBT and open it back, before exporting. Then it will work. Should I file a separate bug report? |
@arvidn has done a recent PR about I2P: |
qBittorrent & operating system versions
qBittorrent: 4.6.0 x64
Operating system: Windows 7 SP1 x64 6.1.7601
Qt: 5.15.8
libtorrent-rasterbar: 2.0.9.0
What is the problem?
Sometimes user may want to obtain non-I2P (clearnet) torrent and convert it to I2P torrent.
Currently it means removing clearnet trackers and adding I2P tracker.
The problem is that despite having only I2P tracker, qBittorrent continues to treat it as clearnet torrent and connects to clearnet peers.
Steps to reproduce
udp://tracker.openbittorrent.com:80
,udp://tracker.opentrackr.org:1337/announce
and add trackerhttp://tracker2.postman.i2p/announce.php
.qBittorrent should not connect to clearnet peers, but it does.
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: