Closed FranciscoPombal closed 3 years ago
arvidn
commented
4 years ago Do you plan on adding it?
It's not very high on my list right now. Maybe there should be a socks5 log alert, instead of the error alert, and it would be controlled by a new alert mask flag.
Cunningcory
commented
4 years ago I had a wave of error messages this morning but am still connected! I believe this is the longest I've gone without it disconnecting and needing a restart. Here are the error messages. The only file I had downloading was just an IP check torrent:
4/29/2020 10:51 AM - Detected external IP: 109.201.154.134
4/29/2020 10:45 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/29/2020 10:44 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 109.201.154.130:1080
4/29/2020 10:00 AM - Detected external IP: 109.201.154.130
4/29/2020 9:55 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 46.166.190.152:1080
4/29/2020 9:36 AM - Detected external IP: 46.166.190.152
4/29/2020 9:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/29/2020 9:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 109.201.154.134:1080
4/29/2020 9:10 AM - Detected external IP: 109.201.154.134
4/29/2020 9:04 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/29/2020 9:03 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/29/2020 9:03 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:02 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:02 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:01 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/29/2020 9:01 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/29/2020 9:01 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.130:1080
4/29/2020 9:01 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.130:1080
4/29/2020 9:00 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.130:1080
4/29/2020 9:00 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 46.166.190.174:1080
4/29/2020 7:40 AM - Detected external IP: 46.166.190.174
4/29/2020 7:34 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.174:1080
4/29/2020 7:33 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/29/2020 7:33 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.134:1080
4/29/2020 7:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/29/2020 7:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/29/2020 7:32 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/29/2020 7:31 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/29/2020 7:31 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/29/2020 7:31 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/29/2020 7:31 AM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 109.201.152.22:1080The errors in the log don't bother me as long as it stays connected!
arvidn
commented
4 years ago that's great. Although, it is a bit disconcerting that the connection to the proxy fails that often. It seems to come in bursts though, so maybe it isn't all that big of a problem.
Cunningcory
commented
4 years ago The connection is no longer working, giving the same symptoms as before (stuck on Downloading metadata). I basically tried to download something during the error message spam. It may eventually reconnect? I'll let it sit for a little while and see. Here are the errors:
4/30/2020 2:37 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.166:1080
4/30/2020 2:35 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.247:1080
4/30/2020 2:34 PM - '********' added to download list.
4/30/2020 2:34 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 2:32 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/30/2020 2:31 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: No connection could be made because the target machine actively refused it ep: 109.201.152.22:1080
4/30/2020 2:30 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/30/2020 2:29 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/30/2020 2:29 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.134:1080
4/30/2020 2:28 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.174:1080
4/30/2020 2:28 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:27 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:27 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:27 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:27 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:26 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 2:26 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 46.166.190.140:1080
4/30/2020 1:57 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/30/2020 1:55 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: No connection could be made because the target machine actively refused it ep: 109.201.152.22:1080
4/30/2020 1:53 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: No connection could be made because the target machine actively refused it ep: 109.201.152.22:1080
4/30/2020 1:51 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: No connection could be made because the target machine actively refused it ep: 109.201.152.22:1080
4/30/2020 1:49 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.186.207:1080
4/30/2020 1:48 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.186.207:1080
4/30/2020 1:46 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.134:1080
4/30/2020 1:45 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.134:1080
4/30/2020 1:44 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: No connection could be made because the target machine actively refused it ep: 109.201.152.22:1080
4/30/2020 1:43 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/30/2020 1:43 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/30/2020 1:42 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/30/2020 1:41 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/30/2020 1:41 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 1:41 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 1:41 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 1:40 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.247:1080
4/30/2020 1:40 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 1:40 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 46.166.190.140:1080You can see I tried to add a torrent at 2:34. As of now the errors are still happening and have been happening for nearly an hour now.
UPDATE: The proxy reconnected for about three minutes. During that time the torrent already in the queue remained unchanged - still refusing to connect. Starting a new torrent, however, worked. After three minutes, however, the errors continued and adding any new torrent refused to work again.
4/30/2020 2:50 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/30/2020 2:49 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
4/30/2020 2:49 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.186.207:1080
4/30/2020 2:48 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.186.207:1080
4/30/2020 2:48 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 2:48 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 2:48 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 2:48 PM - '2nd ******' added to download list. (NOW NO LONGER WORKS AGAIN)
4/30/2020 2:47 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.140:1080
4/30/2020 2:47 PM - '2nd ******' was removed from the transfer list and hard disk.
4/30/2020 2:47 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 46.166.190.166:1080
4/30/2020 2:46 PM - Successfully moved torrent: ******. New path: F:\Downloads\temp
4/30/2020 2:46 PM - '2nd *******' added to download list. (WORKED)
4/30/2020 2:44 PM - Detected external IP: 46.166.190.166
4/30/2020 2:37 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.166:1080
4/30/2020 2:35 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.247:1080
4/30/2020 2:34 PM - '*******' added to download list. (NEVER WORKED)
4/30/2020 2:34 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080UPDATE 2: The proxy eventually reconnected and both files were able to connect and start downloading. For over an hour the proxy was down, spitting out error messages pretty consistently. At least it does seem the torrents will eventually start working again when the client reconnects:
4/30/2020 2:55 PM - Detected external IP: 109.201.154.134
4/30/2020 2:54 PM - Successfully moved torrent: 2nd ******. New path: F:\Downloads\temp
4/30/2020 2:54 PM - Successfully moved torrent: ******. New path: F:\Downloads\temp
4/30/2020 2:51 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.138.237:1080
4/30/2020 2:51 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.152:1080
4/30/2020 2:50 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.152:1080
xavier2k6
commented
4 years ago @Cunningcory What's your OS version build number? & are all network drivers up to date?
Cunningcory
commented
4 years ago Windows 10 Pro 1909 Intel(R) I211 Gigabit Network Connection Driver 12.17.10.8
I'll check for updates to both.
Edit: Updated both (Windows just had an optional update). Network driver is now 12.18.9.6. Had to restart the computer. I continued to receive error messages for a few minutes after restarting but then it stabilized. I now haven't had error messages for about an hour. I assume I'll have another wave of them in a day or so, but we'll see.
4/30/2020 3:21 PM - Detected external IP: 109.201.154.130
4/30/2020 3:20 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 109.201.154.247:1080
4/30/2020 3:16 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 3:16 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.247:1080
4/30/2020 3:16 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 109.201.154.247:1080
4/30/2020 3:16 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 109.201.154.247:1080
4/30/2020 3:14 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 3:14 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 3:13 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 109.201.154.247:1080
4/30/2020 3:13 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 109.201.154.247:1080
4/30/2020 3:13 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.166:1080
4/30/2020 3:12 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 46.166.190.166:1080
4/30/2020 3:12 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 46.166.190.174:1080
4/30/2020 3:11 PM - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 46.166.190.174:1080
4/30/2020 3:11 PM - Successfully listening on IP: 0.0.0.0, port: UDP/53681
crafty35a
commented
4 years ago I'm now up to 3.5 days and everything is still functional. This would have been unheard of before, so at the least the reconnect change seems to have greatly improved the situation.
FranciscoPombal
commented
4 years ago @Cunningcory could have just been instability from the proxy service provider. Do they have a page such as this one (https://www.githubstatus.com/) where you can verify against the timestamps when you had the issues?
Cunningcory
commented
4 years ago I'm using PIA and can't find anything like that - certainly not anything that would show minute by minute. These errors come pretty consistently in waves for about an hour or two maybe twice a day from what I can tell.
FranciscoPombal
commented
4 years ago @Cunningcory
These errors come pretty consistently in waves for about an hour or two maybe twice a day from what I can tell.
Could these times be coinciding with peak hours/maintenance/mandatory reconnection after x hours connected in a row? Or a combination of the 3?
Cunningcory
commented
4 years ago I'm far from an expert, but my understanding is that, for whatever reason, proxy servers often disconnect and reconnect connections. This happens even when running the PIA desktop client and results in the same issue (at least in previous versions) of the torrent client ceasing to work until it is restarted. My solution has been to run a virtual machine with the PIA desktop client, Qbittorrent, and a Qbittorrent babysitter program running. When PIA disconnects and reconnects, the babysitter automatically restarts the torrent client. Not the most ideal solution, which is why I'd love to just get SOCKS5 working.
The difference here is the connection seems to be forcibly closed by "the remote host". There's a timeout and what might be a forced waiting period before allowing reconnect. In the meantime the proxy IP address will often change. I don't know if this is an idle timeout or what. I don't know if the torrent client is doing something that's triggering the disconnect or if it's just the normal ebb and flow of the proxy.
More tech savvy people will probably have a better idea. I'm just trying to interpret the error messages based on my own experience. I will say I don't believe the error messages happen at the SAME time every day.
FranciscoPombal
commented
4 years ago @Cunningcory I would bet it's PIA forcing the disconnect/reconnect, to clean up idle connections. Shoot them a support email - they might give a conclusive response. Ask something like "do your proxies forcefully disconnect or reconnect after a client has been connected for a long time?".
HnyBear
commented
4 years ago I had a long conversation with PIA support about their socks5. They admit it is overloaded and have plans to add another proxy at some point. I've switched to their VPN program in the mean time and am using the split tunnelling in that to connect for all my qbittorrent needs.
FranciscoPombal
commented
4 years ago Great! Looks like on the qBittorrent libtorrent side, everything is solved now. I'll close this once the next stable release of qBIttorrent is released (which will obviously include this libtorrent patch).
Cunningcory
commented
4 years ago @HnyBear I think that's a new feature of PIA. Would this test build reconnect to the proxy when treating it as a whole network? My workaround included setting up PIA on a virtual machine, but every time it disconnected Qbittorrent connections would hang until restart. Have you had that issue?
HnyBear
commented
4 years ago Haven't had enough time to test it. I'll try to let you know if it ends up having issues but PIA's reverse split tunnelling is pretty good so far.
Cunningcory
commented
4 years ago Cool, thanks, I think I'll try the same. I set it up and connected it, ran a torrent, disconnected PIA, waited a minute, and then reconnected and the torrent picked back up. I'm not sure if that's the same as PIA disconnecting itself, though. I'm hoping picking back up the SOCKS5 connection would also apply to picking back up the client connection.
condoghost
commented
4 years ago Windows 7 NordVPN. First open NordVPN Desktop App to connect to country specified P2P Socks5 VPN, in this instance UK1296 but I have done this 5 or 6 times since updating to v4.2.5. I close App, open qBittorrent, set Connection, Proxy Server Socks5 to that working host. Torrents already in client all HTTP trackers load and Working. Load new torrent UDP trackers Working. Leave overnight ... 232 SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: Torrents already in client all HTTP trackers Working. Load new torrent UDP tracker Working. Will continue to monitor ...
UPDATE in the meantime I switched hosts a couple of times and also closed/reopened client a couple of times, and also shut down / restarted PC a couple of times. Since 02/05/2020 10:45 - Detected external IP: 185.253.98.107 there have been no Socks5 proxy errors. I'll keep client running uninterrupted for a few days - if I can keep my wife away from the bloody power switch that is. I will update https://github.com/qbittorrent/qBittorrent/issues/12583#issuecomment-622960888
FranciscoPombal
commented
4 years ago @condoghost Use the test build linked here, it should be able to re-establish connection: https://github.com/qbittorrent/qBittorrent/issues/12583#issuecomment-619298534
crafty35a
commented
4 years ago @condoghost Are you attempting to use VPN and Sock5 proxy at the same time? Sounds like it, since AFAIK the NordVPN app is only needed for VPN, not proxy. Socks5 is not necessary if you are connected to a VPN.
condoghost
commented
4 years ago @condoghost Are you attempting to use VPN and Sock5 proxy at the same time? Sounds like it, since AFAIK the NordVPN app is only needed for VPN, not proxy. Socks5 is not necessary if you are connected to a VPN.
No it doesn't "sound like it" at all. Read through what I wrote again. FIRST I open NordVPN app to obtain a working server ID. Obviously I then CLOSE the app, open client, update and set Connection Proxy Server Socks-5 Host with the "working" host.
condoghost
commented
4 years ago @condoghost Use the test build linked here, it should be able to re-establish connection: #12583 (comment)
Okay I will look at that. In the meantime I switched hosts a couple of times and also closed/reopened client a couple of times, and also shut down / restarted PC a couple of times. Since 02/05/2020 10:45 - Detected external IP: 185.253.98.107 there have been no Socks5 proxy errors. I'll keep client running uninterrupted for a few days - if I can keep my wife away from the bloody power switch that is - and update here ...
UPDATE Haven't installed test build yet, wanted to see how v4.2.5 was running first. 03/05/2020 11:50 24hrs now no further errors reported, http trackers working. Have loaded a number of torrents throughout, observed a few minutes delay longer for udp trackers to start working, manual force reannounce but will leave next time to see if manual force reannounce is actually needed, no issues, no errors. Could be after upgrade to v4.2.5 it took a few re-sets for the client to stabalise or I was just unlucky with setting one host that wasn't so stable. Will update here again in 24hrs or earlier if issues come back ...
FranciscoPombal
commented
4 years ago @condoghost errors are still expected to occur with the test build. However, you should observe that it it's able to recover and reconnect.
amsterdampaul
commented
4 years ago Whilst my problem does not exactly match this on as described. I do have some interesting observations.
I am fortunate to have a lot of machines in the house so have been able to try QBT 4.2.5 on Windows 10 v1909 b18363 and Mac OSX 10.15.4
I have a socks5 proxy from ipvanish.com and I am able to test the same torrent on both the WinPC and the MAC.
I still see constant issues with the Windows version. I have the same settings enabled on MAC and Win versions of 4.2.5 but if I open the torrent on MAC I have 1) hundreds of DHT nodes appear 2) the torrent immediately starts to download and complete. On the Win instance. zero DHT nodes found, UDP trackers never work, on MAC version the complete opposite.
firewall not enabled on either machine.
Willing to provide extra info if this can help anyone find the issue.
arvidn
commented
4 years ago @amsterdampaul Do you get any socks5 errors in the log?
amsterdampaul
commented
4 years ago None no..
WIN
MAC
Can leave the Windows instance for hours and there will be no DHTs and the torrent will not have started downloading.
such a pity that we cannot put the thing into debug2 and get full logging out of it. (not that I know of)
condoghost
commented
4 years ago Windows 7 qBittorrent v4.2.5 Connection Proxy Server SOCKS5 Host NordVPN uk1296 First SOCKS5 proxy errors since https://github.com/qbittorrent/qBittorrent/issues/12583#issuecomment-622960888 02/05/2020 10:45 - Detected external IP: 185.253.98.107... 04/05/2020 00:14 - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 185.253.98.106:1080 04/05/2020 00:14 - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 185.253.98.106:1080 none since, http trackers already loaded are working, have no udp torrents loaded. Loaded first new udp torrents since SOCKS5 proxy error, trackers not working. Force reannounce udp trackers still not working. Deleted and reloaded udp torrents, trackers still not working. This is a great pity because with this version I had the best results ever with udp torrents, some hitting speeds 8.5MB/s, one torrent loading 130-seeds one time [never had such results before with any versions of qBittorrent]. Okay, I've closed this client v4.2.5 and will look at running the test build #12583 (comment)
condoghost
commented
4 years ago Windows 7 Test Build #12583 (comment) "qBittorrent master commit 480e732 with libtorrent patch 4579" Connection Proxy Server SOCKS5 Host NordVPN uk1296 [using same host as with v4.2.5] Loaded 5 new udp torrents, trackers on each started instantly, no errors. Lets see how this goes. Thank-you everyone for your continued hard work. I'll leave this running and add new udp torrents from time to time. Will provide an UPDATE here in 24-hours ...
UPDATE No issues so far with test build. Getting great download speeds for udp torrents - up to 8.5MB/s with some udp torrents [as good as I get with private http torrents] and many hitting 4MB/s. Fantastic numbers for seed connections - one udp torrent had 189-seed connections simutaneously of 200-seeds. Of course that also means high numbers of peer connections and having to manually manage the blocking of those not sharing or grabbing so much more than they share. In my opinion, with this Test Build and v4.2.5, qBittorrent has never been this good for udp trackers using Connection Proxy Server Type SOCKS5. The only SOCKS5 proxy errors I got were when I ran ipleak Torrent Address Detection ... 04/05/2020 13:20 - 'ipleak.net torrent detection' added to download list. 04/05/2020 13:21 - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 185.253.98.106:1080 04/05/2020 13:21 - SOCKS5 proxy error. Message: SOCKS5 error. op: hostname_lookup ec: No such host is known ep: 0.0.0.0:55535 04/05/2020 13:22 - 'ipleak.net torrent detection' was removed from the transfer list. 04/05/2020 13:23 - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: 185.253.98.106:1080 04/05/2020 13:23 - SOCKS5 proxy error. Message: SOCKS5 error. op: hostname_lookup ec: No such host is known ep: 0.0.0.0:55535 04/05/2020 13:23 - SOCKS5 proxy error. Message: SOCKS5 error. op: hostname_lookup ec: No such host is known ep: 0.0.0.0:55535 04/05/2020 13:24 - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 185.253.98.106:1080 04/05/2020 13:24 - SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 185.253.98.106:1080 Thank-you everyone. Looking so much better than just "good" :) Will post new UPDATE comment when the time clock hits 48hrs ...
amsterdampaul
commented
4 years ago Windows 7 Test Build #12583 (comment) "qBittorrent master commit 480e732 with libtorrent patch 4579" Connection Proxy Server SOCKS5 Host NordVPN uk1296 [using same host as with v4.2.5] Loaded 5 new udp torrents, trackers on each started instantly, no errors. Lets see how this goes. Thank-you everyone for your continued hard work. I'll leave this running and add new udp torrents from time to time. Will provide an UPDATE here in 24-hours ...
i have to say I tried that build you mention on my Win10 and I see no difference UDP trackers do not work and I never get any DHT nodes appear. Also no socks5 errors in the log
FranciscoPombal
commented
4 years ago @amsterdampaul Please post your settings file of each machine in plain text, taking care to remove any potentially sensitive data. I'm mainly interested in what you have the "Network Interface" and "optional IP address to bind to" settings set to in the advanced settings.
amsterdampaul
commented
4 years ago @amsterdampaul Please post your settings file of each machine in plain text, taking care to remove any potentially sensitive data. I'm mainly interested in what you have the "Network Interface" and "optional IP address to bind to" settings set to in the advanced settings.
here they are: qbittorrent_4.2.5_windows10.txt qbittorrent_4.2.5_mac-osx.txt
condoghost
commented
4 years ago Windows 7 qBittorrent Test Build #12583 (comment) "qBittorrent master commit 480e732 with libtorrent patch 4579" Connection Proxy Server SOCKS5 Host NordVPN uk1296 [using same host as with v4.2.5] 38hrs: 1,381 SOCKS5 proxy errors between 05/05/2020 23:43 and 06/05/2020 06:47 ... qbittorrent_4.3.0alpha1-2020-05-06-07-18.txt 06/05/2020 06:47 Torrents already loaded: http trackers working. 06/05/2020 06:47 Added udp torrent: all trackers working and torrent instantly starts downloading 06/05/2020 06:55 Added udp torrent: all trackers working and torrent instantly starts downloading 06/05/2020 07:17 and 07:27 14 SOCKS5 proxy errors ... qbittorrent_4.3.0alpha1-2020-05-06-07-25.txt Will leave client running and report again in 24hrs ...
FranciscoPombal
commented
4 years ago @condoghost
06/05/2020 07:17 and 07:27 14 SOCKS5 proxy errors ...
As stated above, errors are expected even with the test build. Some are unavoidable, the proxy can just decide to disconnect you, which will result in an error. However, it should be able to reconnect after the error occurs, unlike the regular build. So the important thing is whether you see qBIttorrent managing to reconnect successfully or not.
crafty35a
commented
4 years ago Quick update- 9+ days of stability here. Looking forward to a stable build with this fix incorporated! Great work to all involved.
condoghost
commented
4 years ago @condoghost
06/05/2020 07:17 and 07:27 14 SOCKS5 proxy errors ...
As stated above, errors are expected even with the test build. Some are unavoidable, the proxy can just decide to disconnect you, which will result in an error. However, it should be able to reconnect after the error occurs, unlike the regular build. So the important thing is whether you see qBIttorrent managing to reconnect successfully or not.
Yes qBittorrent does appear to be managing to reconnect successfully though there is no entry in the execution log that highlights this, just lists of SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: 185.253.98.106:1080 I'm still adding txt file here given every now and then I get SOCKS5 proxy error. Message: SOCKS5 error. op: handshake ec: An existing connection was forcibly closed by the remote host ep: 185.253.98.106:1080 and having continuous lists of error messages must impact the efficiency of the client. Between 06/05/2020 07:28 and 07/05/2020 13:32 there have been 1,702 SOCKS5 proxy error in two distinct time frames: between 06/05/2020 07:28 and 06/05/2020 07:55 when they stopped having loaded two udp torrents and ipleak.net torrent detection to be assured the proxy was indeed connected and working in the client. The second was between 07/05/2020 01:51 and 07/05/2020 13:32 when I loaded a new udp torrent trackers working and downloading automatically without any intervention on my side. No further SOCKS5 proxy errors reported in the Execution Log since. qbittorrent_4.3.0alpha1-2020-05-07-14-06.txt Will leave client running and report again in 24hrs ...
FranciscoPombal
commented
4 years ago @condoghost
Good, I think at this point we have enough confirmation.
Yes qBittorrent does appear to be managing to reconnect successfully though there is no entry in the execution log that highlights this
Such a message could be added later: https://github.com/qbittorrent/qBittorrent/issues/12583#issuecomment-621120307
FranciscoPombal
commented
4 years ago @amsterdampaul
Looks like your Windows config has an extra Connection\ProxyOnlyForTorrents=false that the mac config does not have. Could it be the cause? Other than that, maybe an interface selection problem in qBittorrent? On Windows try setting the interface and IP address to bind to to something specific in the advanced settings.
amsterdampaul
commented
4 years ago @amsterdampaul Looks like your Windows config has an extra
Connection\ProxyOnlyForTorrents=falsethat the mac config does not have. Could it be the cause? Other than that, maybe an interface selection problem in qBittorrent? On Windows try setting the interface and IP address to bind to to something specific in the advanced settings.
good spot, but sadly with both set the same the mac version works perfectly (little snitch shows me it is only using the socks proxy) and the win10 version just doesnt work for me..
But if I fire up Win10 v4.1.9.1 it works just fine, and glaswire shows me that 4.1.9.1 is using the socks proxy.. 4.1.9.1 shows DHT nodes counting up very quickly. 4.2.x has never done that for me.
I guess I am just unlucky and there are not many people who use a socks5 proxy with the latest windows10 versions.
amsterdampaul
commented
4 years ago @amsterdampaul Looks like your Windows config has an extra
Connection\ProxyOnlyForTorrents=falsethat the mac config does not have. Could it be the cause? Other than that, maybe an interface selection problem in qBittorrent? On Windows try setting the interface and IP address to bind to to something specific in the advanced settings.good spot, but sadly with both set the same the mac version works perfectly (little snitch shows me it is only using the socks proxy) and the win10 version just doesnt work for me..
But if I fire up Win10 v4.1.9.1 it works just fine, and glaswire shows me that 4.1.9.1 is using the socks proxy.. 4.1.9.1 shows DHT nodes counting up very quickly. 4.2.x has never done that for me.
I guess I am just unlucky and there are not many people who use a socks5 proxy with the latest windows10 versions.
Actually one more update!.. Using one of the latest builds that have been posted (qBittorrent master commit 480e732 with libtorrent patch 4579 )
and setting the interface and address, I get it worked as expected. and UDP trackers work over the socs5 proxy and DHT nodes start counting up within seconds of starting the GUI..
Now this does seem to be progress! thank you
FranciscoPombal
commented
4 years ago @amsterdampaul but it does not work if listening interface/optional ip to bind to are set to any/any in the advanced settings? I think it should also work in that case.
austinjordan
commented
4 years ago Anyone having trouble with this just FYI I commented on some earlier threads b/c I thought something was wrong with my SOCKS5 proxy or something, turns out if I uncheck the Torrent Queuing option the client works perfectly. May not work for everyone but this solved all the head-aches I was having with occasionally have to restart qBittorrent due to downloads not starting, etc.
FranciscoPombal
commented
4 years ago Anyone having trouble with this just FYI I commented on some earlier threads b/c I thought something was wrong with my SOCKS5 proxy or something, turns out if I uncheck the Torrent Queuing option the client works perfectly. May not work for everyone but this solved all the head-aches I was having with occasionally have to restart qBittorrent due to downloads not starting, etc.
Yeah, the queuing system is a known source of problems. Mainly because it is not really obvious that all started torrents, not just those that have download/upload activity, count towards the "Maximum active torrents" limit. People assume that "Maximum active torrents" should be the sum or maximum or a close approximation of "max active downloads" + "max active uploads". To make matters worse "don't count slow torrents towards limits" does not apply to "maximum active torrrents", just the other 2.
Anyway, this is not the case for @amsterdampaul , as their queuing is disabled.
condoghost
commented
4 years ago @condoghost
Good, I think at this point we have enough confirmation.
Yes qBittorrent does appear to be managing to reconnect successfully though there is no entry in the execution log that highlights this
Perhaps at this point we don't have enough confirmation as to "why so many continuous SOCKS5 proxy errors" when I know this proxy continues working and hasn't been interrupted working during this client session.
Windows 7 qBittorrent Test Build #12583 (comment) "qBittorrent master commit 480e732 with libtorrent patch 4579" No change - still using Connection Proxy Server SOCKS5 Host NordVPN uk1296
Summary of Activity since 07/05/2020 07/05/2020 18:09 Only udp torrent removed from client 07/05/2020 19:23 and 07/05/2020 20:04 42 SOCKS5 errors: SOCKS5 proxy error. Message: SOCKS5 error. op: sock_read ec: End of file ep: All http trackers are status Working 07/05/2020 20:05 ran ipleak Torrent Address detection reports IP address - NordVPN server is working 07/05/2020 20:06 '1st new udp torrent' added to client udp trackers Not Working Forced reannounce udp trackers Not Working 07/05/2020 20:09 ipleak removed from client 07/05/2020 20:11 '2nd udp torrent' added to client udp trackers start Working, data is Downloading Made decision to leave udp torrent Seeding with at least 1-Peer Uploading 09/05/2020 15:20 42-hours since last SOCKS5 proxy error No further errors since 07/05/2020 20:11 qbittorrent_4.3.0alpha1-2020-05-09-14-24.txt Perhaps SOCKS5 proxy errors are only occurring during periods when there are no udp torrents in the client actively seeding. In a single session if I don't have any udp torrents in the client at all, only http torrents Seeding, SOCKS5 proxy errors do not occur. Once I load a udp torrent in the client it appears a short period of time after that single udp torrent is removed - perhaps coincidence perhaps not - SOCKS5 proxy errors occur. When I leave a single udp torrent in the client Seeding with trackers Working and at least 1-Seed Uploading, SOCKS5 proxy errors do not occur.
Thank-you for all your help. I'll not be reporting further on this unless something dramatically changes whilst running this Test Build. Stay Healthy Stay Safe.
crafty35a
commented
4 years ago Probably worth mentioning that I've now been stable for over a month with the test build. Looking forward to a stable release!
xavier2k6
commented
4 years ago Probably worth mentioning that I've now been stable for over a month with the test build. Looking forward to a stable release!
That's great to hear!
(In case you want to give it a whirl) Here's the latest Windows test build of 4.3.0(Alpha1) I compiled with listed libraries:
qBittorrent master | 4.3.0 +git a1faef0
libtorrent-rasterbar | 1.2.6 +git 2622792
Qt | 5.14.2
OpenSSL | 1.1.1g
zlib | 1.2.11
Boost | 1.73I haven't included the Qt 5.15 library as I'm currently having compilation issues with it.
HnyBear
commented
4 years ago Which thread are we suppose to be following for socks 5 issues now? I've lost track.
xavier2k6
commented
4 years ago Which thread are we suppose to be following for socks 5 issues now? I've lost track.
This one (as in - the one you've just posted that question)
arvidn
commented
4 years ago although, if it isn't "issue due to insufficient retries", it would be a bit misleading to post in this thread (since that's its title)
RabidWolf
commented
4 years ago Probably worth mentioning that I've now been stable for over a month with the test build. Looking forward to a stable release!
That's great to hear!
(In case you want to give it a whirl) Here's the latest Windows test build of 4.3.0(Alpha1) I compiled with listed libraries:
qBittorrent master | 4.3.0 +git a1faef0 libtorrent-rasterbar | 1.2.6 +git 2622792 Qt | 5.14.2 OpenSSL | 1.1.1g zlib | 1.2.11 Boost | 1.73I haven't included the Qt 5.15 library as I'm currently having compilation issues with it.
@xavier2k6 What's new with this 1?
condoghost
commented
4 years ago @condoghost
Good, I think at this point we have enough confirmation.
Yes qBittorrent does appear to be managing to reconnect successfully though there is no entry in the execution log that highlights this
Such a message could be added later: #12583 (comment)
Let me just repeat again "No qBittorent does not appear to be managing to reconnect successfully every time" For example, when I close client to shutdown PC. When I reopen client after restarting PC, all torrents with udp trackers are showing Not Working and seeds peers are not listed though some that were downloading before client was closed will actually now start to downloading. I must Forced reannounce on each torrent with udp trackers Not Working once maybe twice maybe three times before udp trackers Working, torrent displays seeds and peers, and those torrents that were not downloading when I restarted the client now start to download. This test build qBittorrent v4.3.0alpha1 (64-bit) is so much better but still we get instances where it is not managing to reconnect successfully every time. Without an entry in the execution log to show reconnect successful as well as an entry to log a Forced reannounce is performed it is difficult to see how this may be progressed for investigation. Is it 'livable with'? Yes, but only if we manually check from time to time that new udp torrents added are indeed Working and existing udp torrents are Working too. Thank-you. Stay healthy stay safe.
EDIT: for users having trouble with this, use the test build linked here: https://github.com/qbittorrent/qBittorrent/issues/12583#issuecomment-619298534, it should be able to re-establish connection after disconnect errors.
Follow up to https://github.com/qbittorrent/qBittorrent/issues/11735#issuecomment-615831521 @arvidn for your convenience.