Add Tracker status column #6881

Closed
opened 2026-02-21 18:39:55 -05:00 by deekerman · 10 comments
Owner

Originally created by @Makishima on GitHub (Feb 14, 2018).

qBittorrent version and Operating System

4.0.3 Win10 x64

What is the problem

I cant easily determinate tracker's status

What is the expected behavior

Additional column with such kind of information

temp_vk_2

Originally created by @Makishima on GitHub (Feb 14, 2018). ### qBittorrent version and Operating System 4.0.3 Win10 x64 ### What is the problem I cant easily determinate tracker's status ### What is the expected behavior Additional column with such kind of information ![temp_vk_2](https://user-images.githubusercontent.com/5548003/36222332-061a35fa-11d2-11e8-8564-d449a4560e0e.png)
deekerman 2026-02-21 18:39:55 -05:00
Author
Owner

@greenbench commented on GitHub (Feb 15, 2018):

Yeah, that would be good. Or for me personally, make it like seeding/leaching/adding/rechecking indication, with a different color.

@greenbench commented on GitHub (Feb 15, 2018): Yeah, that would be good. Or for me personally, make it like seeding/leaching/adding/rechecking indication, with a different color.
Author
Owner

@Ryrynz commented on GitHub (Aug 14, 2018):

in uTorrent the download percentage bar turns red if a tracker isn't working, I'd like to see something similar, ATM I have to look at the Tracker tab to see if a torrent is working.

@Ryrynz commented on GitHub (Aug 14, 2018): in uTorrent the download percentage bar turns red if a tracker isn't working, I'd like to see something similar, ATM I have to look at the Tracker tab to see if a torrent is working.
Author
Owner

@phant commented on GitHub (Dec 9, 2018):

I requesting same behavior like uTorrent - if tracker #0 not working - turn row to red.
And new columns tracker status (tracker #0) and column with reply message.
It helps to find removed or updated torrents.
2018-12-09_22-37-14

@phant commented on GitHub (Dec 9, 2018): I requesting same behavior like uTorrent - if tracker #0 not working - turn row to red. And new columns tracker status (tracker #0) and column with reply message. It helps to find removed or updated torrents. ![2018-12-09_22-37-14](https://user-images.githubusercontent.com/805222/49700678-d563f780-fc03-11e8-8949-0bf798e6410f.png)
Author
Owner

@phant commented on GitHub (Dec 9, 2018):

@Makishima допиши в названии [Wishlist], вдруг зашевелится дело...

@phant commented on GitHub (Dec 9, 2018): @Makishima допиши в названии [Wishlist], вдруг зашевелится дело...
Author
Owner

@jef commented on GitHub (Apr 19, 2019):

looking into this...

@jef commented on GitHub (Apr 19, 2019): looking into this...
Author
Owner

@Ryrynz commented on GitHub (Apr 20, 2019):

Appreciated. It's extremely useful when dealing with multiple trackers and thousands of torrents. Hope you can get it into 4.2.

@Ryrynz commented on GitHub (Apr 20, 2019): Appreciated. It's extremely useful when dealing with multiple trackers and thousands of torrents. Hope you can get it into 4.2.
Author
Owner

@jef commented on GitHub (Apr 21, 2019):

One thing is that the torrent has a tracker member function to get a QList of trackers, so I don't really know what the user is expecting to see. Just the first tracker's status? The other ones may be working, so it's seeding properly, but the first one isn't. I don't know what the user expects.

I'm thinking maybe I would check all the torrents and see if they are all working, but if none of them were, I would report back "Not Working". Let me know what you think.

edit: Looks like @phant was talking thinking that if the first one is down, then report it. I don't know what the user expects/wants.

@jef commented on GitHub (Apr 21, 2019): One thing is that the torrent has a tracker member function to get a `QList` of trackers, so I don't really know what the user is expecting to see. Just the first tracker's status? The other ones may be working, so it's seeding properly, but the first one isn't. I don't know what the user expects. I'm thinking maybe I would check all the torrents and see if they are all working, but if none of them were, I would report back "Not Working". Let me know what you think. edit: Looks like @phant was talking thinking that if the first one is down, then report it. I don't know what the user expects/wants.
Author
Owner

@Ryrynz commented on GitHub (May 26, 2019):

With multiple trackers across thousands of torrents I'd like to be able to sort by Tracker status and see trackers that refusing the connection. Sometimes a tracker may ban a client version or delete the torrent from the tracker, so we simply want to see which torrents have issues.

@Ryrynz commented on GitHub (May 26, 2019): With multiple trackers across thousands of torrents I'd like to be able to sort by Tracker status and see trackers that refusing the connection. Sometimes a tracker may ban a client version or delete the torrent from the tracker, so we simply want to see which torrents have issues.
Author
Owner

@phant commented on GitHub (Jul 22, 2019):

Just the first tracker's status? The other ones may be working, so it's seeding properly, but the first one isn't. I don't know what the user expects.

Most of private trackers with rating system use only one tracker url.
Some of Russian and exUSSR trackers use "retracker.local" as unified url for ISP network for fast downloads.
So usually 1st position is like "http://bt.t-ru.org/ann?pk=" and 2nd pos is "retracker.local".

Bad sign when first tracker's status is something like "torrent not registered".
Status of retracker.local does not matter at all.


More wide solution for this is options like:
Report about torrents with not working trackers (this option turn percentage bar to red)
☑ can't connect to tracker ⊡ first ⊡ any
☑ tracker with message ⊡ first ⊡ any


And column for sorting is necessary too.

@phant commented on GitHub (Jul 22, 2019): > Just the first tracker's status? The other ones may be working, so it's seeding properly, but the first one isn't. I don't know what the user expects. Most of private trackers with rating system use only one tracker url. Some of Russian and exUSSR trackers use "retracker.local" as unified url for ISP network for fast downloads. So usually 1st position is like "http://bt.t-ru.org/ann?pk=<hash>" and 2nd pos is "retracker.local". Bad sign when first tracker's status is something like "torrent not registered". Status of retracker.local does not matter at all. --------------------------------- More wide solution for this is options like: Report about torrents with not working trackers (this option turn percentage bar to red) ☑ can't connect to tracker ⊡ first ⊡ any ☑ tracker with message ⊡ first ⊡ any --------------------------------- And column for sorting is necessary too.
Author
Owner

@FranciscoPombal commented on GitHub (Apr 22, 2020):

This similar enough in spirit to https://github.com/qbittorrent/qBittorrent/issues/9849 that I will close it as a duplicate.

@FranciscoPombal commented on GitHub (Apr 22, 2020): This similar enough in spirit to https://github.com/qbittorrent/qBittorrent/issues/9849 that I will close it as a duplicate.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#6881
No description provided.