starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

WebUI: does not "error" torrent when it has stopped seeding due to being removed from tracker #13198

New issue

Open

opened 2026-02-21 23:40:16 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-21 23:40:16 -05:00

Owner

Originally created by @tyestor on GitHub (Mar 19, 2022).

qBittorrent & operating system versions

qBittorrent-nox 4.4.1
Unraid 6.9.2 (docker)

Issue is prevalent on the latest versions of both Firefox and Chrome.

What is the problem?

qBittorrent-nox 4.4.1 WebUI does not "error" torrent when it has stopped seeding due to being removed from tracker. I have thousands of torrents being seeded and its very difficult to keep track of torrents that could be removed for a variety of reasons without qBt telling me when they have errored. The Windows client does this without issue.

When a torrent has this error it should be filterable in the WebUI, but it isn't.

Originally created by @tyestor on GitHub (Mar 19, 2022). ### qBittorrent & operating system versions qBittorrent-nox 4.4.1 Unraid 6.9.2 (docker) Issue is prevalent on the latest versions of both Firefox and Chrome. ### What is the problem? qBittorrent-nox 4.4.1 WebUI does not "error" torrent when it has stopped seeding due to being removed from tracker. I have thousands of torrents being seeded and its very difficult to keep track of torrents that could be removed for a variety of reasons without qBt telling me when they have errored. The Windows client does this without issue. ![image](https://user-images.githubusercontent.com/4704145/159142859-291a8707-0f78-4b8b-ac3f-c9a31eb912bf.png) When a torrent has this error it should be filterable in the WebUI, but it isn't.

deekerman added the

WebUI

label

2026-02-21 23:40:16 -05:00

deekerman commented

2026-02-21 23:40:23 -05:00

Author

Owner

@tyestor commented on GitHub (Mar 19, 2022):

I guess this is related to these:

#11469 and #9849

@tyestor commented on GitHub (Mar 19, 2022): I guess this is related to these: #11469 and #9849

deekerman commented

2026-02-21 23:40:25 -05:00

Author

Owner

@SawkeeReemo commented on GitHub (Apr 13, 2022):

Just giving this a bump! Been hoping for this for a long time!

@SawkeeReemo commented on GitHub (Apr 13, 2022): Just giving this a bump! Been hoping for this for a long time!

deekerman commented

2026-02-21 23:40:25 -05:00

Author

Owner

@kambala-decapitator commented on GitHub (Jul 13, 2023):

also interested in the fix for WebUI

@kambala-decapitator commented on GitHub (Jul 13, 2023): also interested in the fix for WebUI

deekerman commented

2026-02-21 23:40:25 -05:00

Author

Owner

@xJayson commented on GitHub (Aug 7, 2023):

Man is it hard for the devs to implement this simple feature officially with no need to go searching for workarounds?

Please devs! We implore you to look at this issue and fix it.

@xJayson commented on GitHub (Aug 7, 2023): Man is it hard for the devs to implement this simple feature officially with no need to go searching for workarounds? Please devs! We implore you to look at this issue and fix it.

deekerman commented

2026-02-21 23:40:25 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 12, 2023):

@xJayson Devs have a lot going on. Can you try to rally some folks to look at the code and propose a fix ?

@luzpaz commented on GitHub (Aug 12, 2023): @xJayson Devs have a lot going on. Can you try to rally some folks to look at the code and propose a fix ?

deekerman commented

2026-02-21 23:40:25 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 14, 2024):

This is still hinged on #9849, correct ?

@luzpaz commented on GitHub (Aug 14, 2024): This is still hinged on #9849, correct ?

deekerman commented

2026-02-21 23:40:26 -05:00

Author

Owner

@kambala-decapitator commented on GitHub (Jan 10, 2025):

got tired of checking all the torrents for errors manually and hacked a simple python script that lists completed torrents that have at least one non-working tracker. All you need is to adjust baseUrl to point to your server - string before /api/v2/torrents/.

#!/usr/bin/env python3

import json
from urllib.request import urlopen

baseUrl = 'http://192.168.1.100:8080/api/v2/torrents/'

with urlopen(baseUrl + 'info?filter=completed') as response:
    torrentsList = json.loads(response.read().decode('utf-8'))
    for torrent in torrentsList:
        with urlopen(baseUrl + 'trackers?hash=' + torrent["hash"]) as response:
            trackers = json.loads(response.read().decode('utf-8'))
            for tracker in trackers:
                if tracker["url"] in ["** [DHT] **", "** [PeX] **", "** [LSD] **"]:
                    continue
                if tracker["status"] == 4 or "not registered" in tracker["msg"].casefold():
                    print(f'[{torrent["tags"]}] {torrent["name"]}: {torrent["content_path"]}')

@kambala-decapitator commented on GitHub (Jan 10, 2025): got tired of checking all the torrents for errors manually and hacked a simple python script that lists completed torrents that have at least one non-working tracker. All you need is to adjust `baseUrl` to point to your server - string before `/api/v2/torrents/`. ```python3 #!/usr/bin/env python3 import json from urllib.request import urlopen baseUrl = 'http://192.168.1.100:8080/api/v2/torrents/' with urlopen(baseUrl + 'info?filter=completed') as response: torrentsList = json.loads(response.read().decode('utf-8')) for torrent in torrentsList: with urlopen(baseUrl + 'trackers?hash=' + torrent["hash"]) as response: trackers = json.loads(response.read().decode('utf-8')) for tracker in trackers: if tracker["url"] in ["** [DHT] **", "** [PeX] **", "** [LSD] **"]: continue if tracker["status"] == 4 or "not registered" in tracker["msg"].casefold(): print(f'[{torrent["tags"]}] {torrent["name"]}: {torrent["content_path"]}') ```

deekerman commented

2026-02-21 23:40:26 -05:00

Author

Owner

@scratchmex commented on GitHub (Jul 2, 2025):

Check on

https://github.com/qbittorrent/qBittorrent/pull/22166

Should be released by 5.2

@scratchmex commented on GitHub (Jul 2, 2025): Check on https://github.com/qbittorrent/qBittorrent/pull/22166 Should be released by 5.2

deekerman commented

2026-02-21 23:40:26 -05:00

Author

Owner

@Zageron commented on GitHub (Jul 3, 2025):

Check on

#22166

Should be released by 5.2

You're a legend. Thanks for finally adding this feature! Looking forward to 5.2 and allowlists. 😎

@Zageron commented on GitHub (Jul 3, 2025): > Check on > > [#22166](https://github.com/qbittorrent/qBittorrent/pull/22166) > > Should be released by 5.2 You're a legend. Thanks for finally adding this feature! Looking forward to 5.2 and allowlists. 😎