mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
teh tracker status "not working" #5766
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#5766
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 @rsgabriel on GitHub (Jul 9, 2017).
Please provide the following information
qBittorrent version and Operating System:
3.3.10, Windows Server 2012
What is the problem:
All trackers except teh are "Working"
What is the expected behavior:
Tracker status to be "Working"
Steps to reproduce:
Unknown
Extra info(if any):
When I visit my announce URL I get a response "nothing to see here". Using another client on the same machine I am able to dl/seed torrents.
I previously encountered this issue in April when I upgraded to 3.3.12, and downgrading to 3.3.10 resolve the issue for me.
I've run into this a few times since but restarting the client has fixed the issue.
Now restarting has no effect. and I can consistently reproduce this issue. Will to run any debug version or collect any logs.
@rsgabriel commented on GitHub (Jul 23, 2017):
It seems pausing and resuming the torrent can (sometimes) fix the error condition for this tracker's torrents.
@rsgabriel commented on GitHub (Jul 27, 2017):
i started a torrent in another client from teh, and then switched back to qbittorent and start/stopped the torrents can also resolve the error condition.
this remains the only tracker affected by this issue
@rsgabriel commented on GitHub (Sep 8, 2017):
now seeing this issue on ggn
@ngosang commented on GitHub (Sep 16, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.