
(N) T21:20:23 - Options were saved successfully. (I) T21:20:22 - IP geolocation database loaded. (I) T21:20:22 - Local Peer Discovery support (N) T21:20:22 - Using config directory: C:/Users/Amit/AppData/Roaming/qBittorrent/ Useful alerts to enable in this case are port_mapping and tracker. It would also be nice if you can try reproducing with libtorrent's client_test. start qBittorrent and do the workaround procedure.I recommend using a "known good" torrent for testing, to isolate as many variables as possible: Please try to get a log that captures only a single session where you do the whole workaround of starting, connecting to the mobile network, and disconnecting from it, which results in the client working like you said. This leads me to believe this is almost for sure a network configuration issue on your end, that gets "accidentally" fixed by the connect/disconnect from the mobile network somehow.īut it's not easy to tell, exactly what happens especially in a concatenated log spanning many different sessions. Like a lot of the times qBittorrent tries to listen on all addresses, but all of them are localhost (127.0.0.1) or link-local addresses (,.
