You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: SOCKS connection failed. Network unreachable.
at Socket.<anonymous> (/Users/ronagy/GitHub/public/tmp/node_modules/socks5-client/lib/Socket.js:246:25)
at Object.onceWrapper (node:events:483:26)
at Socket.emit (node:events:376:20)
at addChunk (node:internal/streams/readable:311:12)
at readableAddChunk (node:internal/streams/readable:286:9)
at Socket.Readable.push (node:internal/streams/readable:225:10)
at TCP.onStreamRead (node:internal/stream_base_commons:192:23)
@aicanfly there are several companies like nearForm that offer paid development services and can do this sort of fix. I am not sure if @ronag or @mcollina (or any other stream maintainers) are up for working on this but you are welcome to shoot them an email to discuss. It's a pretty typical/common format.
Activity
ronag commentedon Feb 25, 2021
Please provided a minimal repro example.
SFx2018 commentedon Feb 25, 2021
works with v15.6.0, doesn't work with v15.10.0 - Error: socket hang up
I filled it with free socks5 proxy.
ronag commentedon Apr 25, 2021
Sorry but the sample is unrunnable:
Error: SOCKS connection failed. Network unreachable. at Socket.<anonymous> (/Users/ronagy/GitHub/public/tmp/node_modules/socks5-client/lib/Socket.js:246:25) at Object.onceWrapper (node:events:483:26) at Socket.emit (node:events:376:20) at addChunk (node:internal/streams/readable:311:12) at readableAddChunk (node:internal/streams/readable:286:9) at Socket.Readable.push (node:internal/streams/readable:225:10) at TCP.onStreamRead (node:internal/stream_base_commons:192:23)ronag commentedon Apr 25, 2021
Tried to repro without request (which is no longer maintained):
It's just stuck. Not Node related.
ronag commentedon Apr 25, 2021
I can confirm it works with Node v15.5.1 but not Node v16.
socks5 seems to be messing with Node internals. I think we need help from the package developer to debug this.
mattcg commentedon May 28, 2021
Hi @aicanfly I am interested in fixing this but am busy on some other projects. Would you be willing to submit a PR?
benjamingr commentedon Jul 1, 2021
@aicanfly there are several companies like nearForm that offer paid development services and can do this sort of fix. I am not sure if @ronag or @mcollina (or any other stream maintainers) are up for working on this but you are welcome to shoot them an email to discuss. It's a pretty typical/common format.
wintercounter commentedon Aug 17, 2021
Had the same issue, switched to
socks-proxy-agent, works fine for me.a7md0 commentedon Oct 8, 2022
Issue still persisting
bnoordhuis commentedon Oct 9, 2022
Since it appears to be an issue with the library and not node itself, I'm going to close out this issue as non-actionable.