qBittorrent
qBittorrent copied to clipboard
Embedded tracker not functional
qBittorrent & operating system versions
qBittorrent: 4.6.5 x64 Operating system: Windows 11 Pro x64 Qt: 6 libtorrent-rasterbar: 2
What is the problem?
So i turned on the embedded tracker setting in advanced along with the port forward on embedded tracker Switched my address mode to ipv6 only, so qbittorent is only binding to ipv6 addresses ( no v4)
I create a new test torrent using hybrid, auto size and the tracker name which is : http://your_public_ip:9000/announce
Basically i followed all instructions at the wiki
Now i create a new torrent, all good, i load it up in transmission and my tracker is working ( ipv6 port forwarded on external sites shown at port 9000 for the tracker). Transmission or other clients can see my Tracker but they cannot find the peer .
Setup : Same local machines, 2 different torrent clients with distinct port numbers .
My question is, that is a basic test of the embedded tracker, which it failed. Is the embedded tracker working or is it bugged out?
Steps to reproduce
1- Bind to ipv6 addresses only on qbittorent 2- Create a hybrid torrent with GUA ipv6 address (what ur qbit client is binded to) 3- Use another client on local machine with different port to download torrent 4- Unable to download
Additional context
^ Tracker supposedly working
Log(s) & preferences file(s)
No response
In my scenario
Transmission says :
I got my test to work with tixati being the other client, but both transmission and bittorent fail
In my scenario Transmission says :
According to this screenshot you've "got a list of 2 peers" from tracker.
Yes that shows that mabye the tracker has connected to the second client, but the complete function of the 2 peers connecting is not happening
I have been able to get the file transfers to work, but it is restart random. I add a new torrent in qbittorent it doesnt connect.Then I restart qbittorent and tixati and the files start to work.
Embedded tracker works fine over ipv6 using public address, tested.
This ticket has been closed.
Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.
-
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.
-
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
-
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.
-
A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
-
Thank you for your contribution(s).
