search

rofl0r / proxychains-ng

proxychains ng (new generation) - a preloader which hooks calls to sockets in dynamically linked programs and redirects it through one or more socks/http proxies. continuation of the unmaintained proxychains project. the sf.net page is currently not updated, use releases from github release page instead.
http://sourceforge.net/projects/proxychains-ng/files
GNU General Public License v2.0
9.82k stars 1.08k forks source link

SOCKS5 with user auth / NordVPN issues #221

Open matutetandil opened 6 years ago

matutetandil commented 6 years ago

I'm trying to use proxychains4 with NordVPN. NordVPN username is my email, so it contains an @ in the middle. I'm trying to put my username like user@domain.com or using 'curl' format: user%40domain.com (replacing the @ with %40). I didn't get an error with any of those, but I got a reject when I try to connect.

For this example, I'm using two servers, the first one is a socks5 in my local in port 3000, and the other is with NordVPN. This is the output I'm getting:

proxychains4 curl www.google.com [proxychains] config file found: /usr/local/etc/proxychains.conf [proxychains] preloading /usr/local/Cellar/proxychains-ng/4.12_1/lib/libproxychains4.dylib [proxychains] DLL init: proxychains-ng 4.12 [proxychains] Strict chain ... 127.0.0.1:3000 ... 190.105.235.89:1080 ... www.google.com:80 <--denied curl: (7) Couldn't connect to server

This is my configuration: strict_chain proxy_dns tcp_read_time_out 15000 tcp_connect_time_out 8000 socks5 127.0.0.1 3000 socks5 190.105.235.89 1080 username%40domain.com password

I also tried username@domain.com, same result

Of course, I tested the proxy server using curl, and works ok, so there are no issues with my username or password.

rofl0r commented 6 years ago

pls try the fix and tell us if it works, thx

matutetandil commented 6 years ago

ok, I'll let you know, I just asked NordVPN to change my username to something without @, so I cannot test it. If someone else can do it, will be great!

rofl0r commented 6 years ago

the @ was unrelated to the bug

rofl0r commented 6 years ago

reopening this since i got word from other nord users that the issue is not resolved also someone was complaining that the bugfix was breaking his use case (but he didn't provide details) https://github.com/rofl0r/proxychains-ng/commit/06c20ed394a65cc9e959a30ea74b8b256f76c1fa

rofl0r commented 6 years ago

term 1

~/cdev/cdev/microsocks[master*]$ ./microsocks -u user@host -P passw0rd

term2

~/proxychains-ng[master]$ cat test.conf
dynamic_chain
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
socks5 127.0.0.1 1080 user@host passw0rd

~/proxychains-ng[master]$ ./proxychains4 -f test.conf curl ifconfig.me
[proxychains] config file found: test.conf
[proxychains] preloading ./libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.12-git-15-gbb30d86
[proxychains] Dynamic chain  ...  127.0.0.1:1080  ...  153.121.72.212:80  ...  OK
XXX.XXX.XXX.XXX
~/proxychains-ng[master]$

term 1

client[4] 127.0.0.1: connected to 153.121.72.212:80

proof that it works with or without @ with microsocks

so my suspicion would be that NordVPN's socks5 service does something odd...

rofl0r commented 6 years ago

@matutetandil i pushed a potential fix, it'd be great if you could give current git master a try to see if we can finally close this issue.

matutetandil commented 6 years ago

@rofl0r Sure! I'll try it during the day, and I'll let you know! Cheers!

rofl0r commented 6 years ago

@matutetandil ping! it'd be really great if you could test soon, as i plan to make a release once the issue is fixed.

rofl0r commented 6 years ago

i think this is solved as of 4.13. feel free to reopen if there are still issues.

rofl0r commented 5 years ago

it seems there are still issues with nordvpn. reopening.

da41b94c commented 1 year ago

Ensure that the authentication credentials are entered correctly. For example, at NordVPN, the authentication credentials differ from the login-password pair used to access your account. To get the username and password, you need to click the "Manual setup" button in your account. These details should be used in the line socks5 ip 1080 username password in the configuration file /etc/proxychains.conf.