simple-socks icon indicating copy to clipboard operation
simple-socks copied to clipboard

Published 20 hours ago • verified publisher icon brozeph

Upstream Proxy Server

Open bacnt2412 opened this issue 2 years ago • 5 comments

I am interested in using your server in the folowing configuration. We currently have SOCKS5 proxies that do not support authentication. We'd like to have this setup:

CLIENT ---> SIMPLE-SOCKS ---> REMOTE_PROXY ---> WEB/WHATEVER

bacnt2412 avatar Sep 20 '22 09:09 bacnt2412

hi @bacnt2412, thank you for sharing this use case. Is it that you would like to be able to associate a remote proxy to the simple socks server for upstream communication at the time you configure it? Any other context could be helpful too... not sure what to ask exactly, but trying to get a sense of how you envision or would like to work with simple-socks in this scenario.

brozeph avatar Oct 03 '22 23:10 brozeph

same https://www.npmjs.com/package/proxy-chain have option "upstreamProxyUrl". But proxy-chain don't support socks5

bacnt2412 avatar Nov 08 '22 03:11 bacnt2412

Same issue. Any updates?

koalex avatar Sep 13 '23 04:09 koalex

Same issue. Wants to support it.

zhangyc310 avatar Mar 14 '24 13:03 zhangyc310

I’ve been reviewing the RFC and researching more about chaining proxy requests over socks. I think what might help you is something like the proxychains utility (https://github.com/rofl0r/proxychains-ng).

To effectively specify an upstream server that is another proxy (and so on and on), the CONNECT portion of the exchange would need to contain the second proxy details, but there is no specification for supplying auth or even further downstream proxies (https://datatracker.ietf.org/doc/html/rfc1928#section-4). Would the proxychains utility help you in this scenario?

brozeph avatar Mar 16 '24 15:03 brozeph