After restarting twice, two UDP trackers are now listed as working. When not working, all trackers are listed "Not working". Restarting client first time did not fix. This also didn't work, though its status is "Stalled" instead of "Downloading metadata" and does list the file size (whereas the magnet files stay at 0). torrent file of that same magnet link and tried to start the torrent from the file. I then re-clicked a magnet link that had worked earlier and it also failed to work. I left the client running and hours later it auto-fetched via RSS some other torrents which failed to work. When I clicked on magnet links to test initially, they worked.
4.0.4 appears to be behaving just like 3.3.16 for me. Qbittorent: 05 01 00 (indicating the auth method is no auth) When the socks5 does not require authentication, the udp trackers work fine and following exchange happens: SOCKS5 : 05 02 (accepting the username/password authentication) Qbittorent: 05 01 02 (indicating the auth method is username/password authentication) After running a socks5 proxy server with authentication required and connecting to it with my qbittorent, I have seen the following exchange: The problem is caused by the SOCKS5 client implementation. http trackers work however the udp ones do not. Steps to reproduceĬhoose socks5 as the proxy to use, enable authentication, download a torrent with udp trackers. The UDP trackers should connect and start working when the SOCKS5 proxy requires authentication. When using SOCKS5 proxy server with username/password authentication UDP trackers indicate "Not working", when the SOCKS5 server does not require authentication, the UDP trackers start working. V3.3.13 MacOS High Sierra What is the problem
0 kommentar(er)
