Closed jeffreybacker closed 10 years ago
What qbt version and what libtorrent version?
qbt 3.1.3 libtorrent 0.16.12 (rasterbar)
Does the gui version behave the same way with that proxy? Have you tried other bt clients with that proxy?
The GUI version does indeed act the same way, though it took several days to make it happen. Perhaps a coincidence, but only could make new torrents stall when adding them via a watch folder.
I've tried Deluge with this same proxy, and it was terrible - no tracker connections. qbt works much better than Deluge.
So far on Linux, Vuze is the only client I've tried that works with SOCKS5 proxy reliably, but I really didn't like Vuze for other reasons. On Windows, utorrent works fine with same proxy.
This is likely a problem with libtorrent and not qbittorrent. Update to libtorrent 0.16.13 when possible. If it still persists either comment here or create a bug issue here: http://code.google.com/p/libtorrent/issues/list (and post the bug link here)
Been running qbt built with libtorrent 0.16.13 for a couple of days, and so far not having any connection issues, even when using same SOCKS5 proxy.
ok. closing. thanks for reporting back.
I'm running qBittorrent on a headless server using qbittorrent-nox in a detached GNU screen. OS is Arch Linux, up to date. I use an authenticated SOCKS5 proxy.
If qbittorrent is left running for more than 24 hours (approximately), any new torrents added will report all trackers as "not working" and no peer connections will be established. An immediate restart of qbittorrent-nox will sometimes fix the problem. Stopping and then starting again after a few minutes always results in peers connecting.
There are no errors indicated in the execution log, but I can try to track down more useful info if you point me in the right direction.
Currently, I have a cron job scheduled to stop qbittorrent and then start it again (via systemd service) after 5 minutes every night, and this effectively works around the problem.