Closed benkaiser closed 5 years ago
Looks like once this is merged it will resolve: https://github.com/TooTallNate/node-socks-proxy-agent/pull/22
Until then I'm resorting to taking a dependency on the fork via adding:
"socks-proxy-agent": "tynopet/node-socks-proxy-agent#bug/proxy-authentication",
to my dependencies and:
"socks-proxy-agent": "tynopet/node-socks-proxy-agent#bug/proxy-authentication"
to my "resolutions" in my package.json.
Also a separate issue is that you can't currently use domains with the socks library, see this issue: https://github.com/JoshGlazebrook/socks/issues/41
I'm setting my proxy when creating the session like this:
Where PROXY_URL looks like (with authentication params masked):
socks5://user:password@proxy-nl.privateinternetaccess.com:1080
If I use curl with the same socks5 proxy it works just fine: