mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Problems with converting non-I2P torrent to I2P torrent #15057
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#15057
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Vort on GitHub (Oct 23, 2023).
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/announceand 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
@Pat-JK commented on GitHub (Oct 24, 2023):
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.
@glassez commented on GitHub (Oct 24, 2023):
@Vort
I believe it is
libtorrentresponsibility.Seems like
libtorrentmark torrent as non-i2p once it is loaded and don't change this flag when trackers are changed.I wonder what happens if you restart qBittorrent after you've changed trackers.
@Vort commented on GitHub (Oct 24, 2023):
If I remember correctly, libtorrent allows clients to change I2P status of torrent.
Not the best solution, but may be worth using.
I2P status is detected correctly after client restart.
Another hack is to add torrents with manually edited magnet links.
By the way,
http://tracker2.postman.i2p/announce.phpis lagging for some reason, so here is another tracker for testing:http://opentracker.dg2.i2p/a.@glassez commented on GitHub (Oct 25, 2023):
@Vort
I mean that
libtorrentshouldn't allow to put torrent to such an incorrect state.If a torrent with only an i2p tracker(s) (it doesn't matter if it was originally or as a result of replacing trackers) and the disabled mixed mode should not connect to clearnet peers, then the fact that it does this is an obvious
libtorrentbug, IMO.@arvidn?
@anikey-from-i2p commented on GitHub (Aug 6, 2024):
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?
@Neustradamus commented on GitHub (Jan 27, 2025):
@arvidn has done a recent PR about I2P:
@xavier2k6 commented on GitHub (Mar 16, 2025):
Well, if it's not a duplicate of this or you can provide more context/submit a PR if possible - then go ahead but just make sure you are using latest qBittorrent 5.0.4.