mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
"Not Working" on all trackers after restarting qBittorrent or resuming system from suspend #5047
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#5047
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 @andoruB on GitHub (Dec 26, 2016).
I've had this issue for a few versions now (the latest version I'm currently using is 3.3.10), and whenever I stop and start qBittorrent, or when I resume the PC from suspend, all the trackers show up as "Not Working", and most of the torrents have them stay that way for hours afterwards. This leaves me with no option but to stop all the torrents, then start them again, which causes a lot of disk writes. Or also to manually reannounce to all torrents manually, which would be quite a daunting task for all the +800 torrents I have loaded in the client... Even though I have "Always announce to all trackers" enabled in the settings, it still doesn't seem to do it... Anything I could do to fix this issue?
@andoruB commented on GitHub (Jun 9, 2017):
Seems to be working fine as of the current version (3.3.13)