mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Connection to SOCKS5 proxy repeatedly times out #11129
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#11129
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 @hagamablabla on GitHub (Oct 27, 2020).
Please provide the following information
qBittorrent version and Operating System
qBittorrent x64 v4.3.0.1
Windows 10.0.18363 Build 18363
What is the problem
qBittorent is unable to connect to peers or trackers because the connection to the SOCKS5 proxy times out. Disabling the proxy allows the connection to go through again.
What is the expected behavior
Connection should go through while the proxy is active
Steps to reproduce
Network interface: Any interface
Extra info(if any)
I've tried using both the regular and service authentication for Nord, as well as both ports 80 and 1080.
Occasionally peers will be found through PeX, but no data actually flows to or from them.
Log:
2020-10-27 14:05 - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 185.XXX.XXX.XXX:1080
2020-10-27 14:05 - Couldn't download IP geolocation database file. Reason: An unknown network-related error was detected
2020-10-27 14:05 - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 185.XXX.XXX.XXX:1080
2020-10-27 14:05 - SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep: 185.XXX.XXX.XXX:1080
2020-10-27 14:05 - Python detected, executable name: 'python', version: 3.8.5
2020-10-27 14:05 - Successfully listening on IP: 0.0.0.0, port: UDP/27600
2020-10-27 14:05 - Options were saved successfully.
2020-10-27 14:05 - Couldn't load IP geolocation database. Reason: The system cannot find the path specified.
2020-10-27 14:05 - UPnP / NAT-PMP support [ON]
2020-10-27 14:05 - Encryption support [ON]
2020-10-27 14:05 - Anonymous mode [ON]
2020-10-27 14:05 - PeX support [ON]
2020-10-27 14:05 - Local Peer Discovery support [ON]
2020-10-27 14:05 - DHT support [ON]
2020-10-27 14:05 - HTTP User-Agent is 'qBittorrent/4.3.0.1'
2020-10-27 14:05 - Peer ID: -qB4301-
2020-10-27 14:05 - Trying to listen on: 0.0.0.0:27600,[::]:27600
2020-10-27 14:05 - Using config directory: C:/XXXXX
2020-10-27 14:05 - qBittorrent v4.3.0.1 started
@Ezekial711 commented on GitHub (Oct 30, 2020):
FYI this may be an issue with NordVPN, not qbittorrent:
At the moment our SOCKS5 protocol is receiving an optimization rework. While this rework is being performed, the majority of servers have this protocol shut down until completion of the rework. It is also not a certainty that it will be available again in the previous locations, and we are collecting user feedback to determine that. As we are still in an early stage of the rework, at this time we do not have an ETA of completion.
Please try using Socks5 servers below:
Ireland SOCKS #5 - 196.196.192.51
Ireland SOCKS #3 - 196.196.192.19
Ireland SOCKS #4 - 196.196.192.59
Ireland SOCKS #2 - 196.196.192.11
Ireland SOCKS #1 - 196.196.192.3
Sweden SOCKS #5 - 196.196.244.75
Sweden SOCKS #3 - 196.196.244.19
Sweden SOCKS #4 - 196.196.244.51
Sweden SOCKS #2 - 196.196.244.11
Sweden SOCKS #1 - 196.196.244.3
@Aerasyn commented on GitHub (Feb 22, 2021):
While, yes, Nord is messing with their socks5 servers, I am able to get a list of the working ones with this powershell command:
$nordservers = Invoke-WebRequest -Uri https://nordvpn.com/api/server -UseBasicParsing -Method GET | ConvertFrom-Json; $nordservers | Where-Object features -match "socks=True" | Select-Object name, domain | Sort-Object name
I tested a working server. Am able to get it to connect on qbit version 4.1.9.1 and none thereafter. Its some kind of issue. Connection error on every version after 4.1.9.1with verified-working nord socks5 servers.
@Zymerdrew commented on GitHub (Apr 30, 2021):
Thank you, Aerasyn! This PowerShell script worked for me. For those who don't want to run some rando's PS script on their computer, these were my results Apr 30, 2021:
name domain
Ireland SOCKS #1 socks-ie1.nordvpn.com
Ireland SOCKS #2 socks-ie2.nordvpn.com
Ireland SOCKS #3 socks-ie3.nordvpn.com
Ireland SOCKS #4 socks-ie4.nordvpn.com
Ireland SOCKS #5 socks-ie5.nordvpn.com
Netherlands SOCKS #1 socks-nl1.nordvpn.com
Netherlands SOCKS #2 socks-nl2.nordvpn.com
Netherlands SOCKS #3 socks-nl3.nordvpn.com
Netherlands SOCKS #4 socks-nl4.nordvpn.com
Sweden SOCKS #1 socks-se1.nordvpn.com
Sweden SOCKS #2 socks-se2.nordvpn.com
Sweden SOCKS #3 socks-se3.nordvpn.com
Sweden SOCKS #4 socks-se4.nordvpn.com
Sweden SOCKS #5 socks-se5.nordvpn.com
United States SOCKS #1 socks-us1.nordvpn.com
United States SOCKS #10 socks-us10.nordvpn.com
United States SOCKS #11 socks-us11.nordvpn.com
United States SOCKS #12 socks-us12.nordvpn.com
United States SOCKS #13 socks-us13.nordvpn.com
United States SOCKS #14 socks-us14.nordvpn.com
United States SOCKS #15 socks-us15.nordvpn.com
United States SOCKS #2 socks-us2.nordvpn.com
United States SOCKS #3 socks-us3.nordvpn.com
United States SOCKS #4 socks-us4.nordvpn.com
United States SOCKS #5 socks-us5.nordvpn.com
United States SOCKS #6 socks-us6.nordvpn.com
United States SOCKS #7 socks-us7.nordvpn.com
United States SOCKS #8 socks-us8.nordvpn.com
United States SOCKS #9 socks-us9.nordvpn.com
For the algorithm: qbittorent
"SOCKS5 proxy error. Message: SOCKS5 error. op: connect ec: timed out ep:"
"Downloading metadata"
NordVPN SOCKS servers not working
@Aerasyn commented on GitHub (Apr 30, 2021):
Any Luck getting them to connect on any version past 4.1.9.1?
@Zymerdrew commented on GitHub (Apr 30, 2021):
Yes - I'm on qbittorent v4.3.4.1 and added one by their name as displayed above (not IP#.) Now it's working great.
@Aerasyn commented on GitHub (Apr 30, 2021):
Weird, I'm still getting the proxy error as I have gotten with every version after 4.1.9.1 :( Even after changing the server. verified working on 4.1.9.1 but not 4.3.4.1 for me still unfortunately.
@Zymerdrew commented on GitHub (May 3, 2021):
Hmm... I had the same issue again today, so I changed to a different server, RESTARTED QT and it worked again.
Aerasyn, I noticed recently that even when I quit QT, it was still running in Task Manager - try looking there and killing the process if running after updating the proxy server location.
I also updated to the newest version (v4.3.5 x64) today, and it kept working.
@Aerasyn commented on GitHub (May 3, 2021):
Yeah, the issue of QB still running in the task manager gets me too, and the servers sometimes not connecting is pretty common. I just switch to one of the others when that happens. But I am def curious about your results. Could you screen-shot the execution log in QB reporting the nord ip address connecting? Anytime i try a version of QB past 4.1.9.1 it always gives me the response from my previous posts screen-shot with that error. Only 4.1.9.1 gives me confirmation that it is connecting to Nord server and shows the ip address as connected. I've been trying every version since this one and nothing for me. Always the error :\ I always get OP's issue
@Zymerdrew commented on GitHub (May 4, 2021):
@Aerasyn commented on GitHub (May 4, 2021):
Oh, that would be regular info you get whether you are connected to a proxy or not, typically. The way I know the proxy is working is that it reports a different ip address than my actual one in that list. like this:
And instead of this desired effect I always get the error from that other picture i posted on every version past 4.1.9.1
@Zymerdrew commented on GitHub (May 5, 2021):
Yes, I also get one of these External IP entries - it shows up a little later in the logs.
@Aerasyn commented on GitHub (May 5, 2021):
Well, if you have verified that the ip address shown last, near the top of the list, is Nord's. Mine will usually show my own actual ip, then after the proxy connects, it shows the one from Nord, so that 2 ip address are visible to me in that list. I hope you're right :) But no matter what I do, I always get OP's issue with the proxy error. I'll be staying on 4.1.9.1 till I can visually see it connect without error. But i'll keep checking with every release. Have a good one.
@Zymerdrew commented on GitHub (May 5, 2021):
Yes - I confirmed it's Nord's IP.
@Aerasyn commented on GitHub (May 5, 2021):
Then I must def be missing something lol. Oh well, 4.1.9.1 has always worked for me anyway. But I can't for the life of me get any other s to work. :\ C'est la vie
@hagamablabla commented on GitHub (May 22, 2021):
Closing this for now since the problem seems to have been fixed for me.
@FranciscoPombal commented on GitHub (May 22, 2021):
If anyone has any issues with the latest version, please open a new issue report, after confirming it is also not an issue on the proxy's side.
Thank you for your contributions.