ProxyAgent: support socks5 protocol

This would solve...

Using the socks5 proxy.

The implementation should look like...

import { ProxyAgent } from 'undici'
const client = new ProxyAgent('socks5://127.0.0.1:7890/')

I have also considered...

Additional context

This would be amazing, but it'd also be somewhat feasible to create it outside of this module. I recommend that route at this point as we are stretched really thin.

It would be best if it could be integrated in this module.

PRs are welcomed.

have you tried https://github.com/Kaciras/fetch-socks?

have you tried https://github.com/Kaciras/fetch-socks?

https://github.com/Kaciras/fetch-socks/blob/master/package.json#L34

This package depends on an undici. So I don't think it's ideal.

the caret means it supports undici versions of at least 5.22.1

the caret means it supports undici versions of at least 5.22.1

When I use undici, it installs one more on its side, which will now will exist two undici.

you can probably use dedupe

Wouldn't it be simpler to make a buildConnector for each type of proxy and use it as a connector?

const httpProxyBuildConnector = (proxy) => {
 return (opts) => {
    const socket = createConnection(opts);
    return socket;
  }
}

const socksProxyBuildConnector = (proxy) => {
  return (opts) => {
    const socket = createConnection(opts);
    return socket;
  }
}

const proxyConnector = httpProxyBuildConnector(proxy);
const proxyAgent = new Agent({connect: proxyConnector });

const resp = await fetch('localhost:3000/', {
  dispatcher: proxyAgent
});

Or you can do it the same way as done by aiohttp in python (https://github.com/Slzdude/aiohttp-proxy)

Also after implementation SOCKS5 - we have got CRITICAL Vulnerability ❌ CVE-2023-38545 which affected on the security.

If no one is working on it I am interested in picking it up, as I am working on nodejs/node#57165 I think it would be a great addition for Node.js built fetch to work more seamlessly with socks 5 proxies. The lack of support of it was one of the reasons I added the local README config in node-core-utils as a workaround (because if you try to fetch github raw content within Chinese GFW you get connection issues). It would also help closing nodejs/node-core-utils#653 and overall making Node.js easier to use for developers in China (socks5 is very popular in China).

Go for it, I believe hasn't been progress since then

feat: implement SOCKS5 proxy support (Phase 1)

Not just socks5:// but also socks5h, for dns resolution through the proxy, which is often critical.

Hi Team,

Thanks for all your hard work!

Just a friendly reminder from a happy user: would it be possible to share an update on when PR #4385 will be merged?

Thanks again!

feat: implement SOCKS5 proxy support (Phase 1)

feat: add SOCKS5 proxy support to ProxyAgent (#4385)

Navigation Menu

Repository navigation

ProxyAgent: support socks5 protocol #2224

This would solve...

The implementation should look like...

I have also considered...

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

ProxyAgent: support socks5 protocol #2224

Description

This would solve...

The implementation should look like...

I have also considered...

Additional context

Activity

mcollina commented on Aug 24, 2023

idranme commented on Aug 24, 2023

mcollina commented on Aug 24, 2023

KhafraDev commented on Aug 25, 2023

idranme commented on Aug 25, 2023

KhafraDev commented on Aug 25, 2023

idranme commented on Aug 26, 2023

KhafraDev commented on Sep 5, 2023

PandaWorker commented on Sep 9, 2023

eugenepugach commented on Nov 9, 2023

joyeecheung commented on Mar 5, 2025

metcoder95 commented on Mar 7, 2025

grepsuzette commented on Sep 8, 2025

AffiTheCreator commented on Dec 22, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions