Getting 'err_no_supported_proxies' in Puppeteer with SOCKS5h – Any Fixes? or Puppeteer 'err_no_suppor

Title: *Puppeteer 'err_no_supported_proxies' when using SOCKS5h – How to Resolve?*

Hey folks,

Ran into this annoying error *err_no_supported_proxies* while trying to use a SOCKS5h proxy with puppeteer.

Tried the usual stuff like checking the proxy URL format (`socks5h://user:pass@ip:port`), even switched to `socks5://` but no luck.

Anyone else hit this?

Weird thing is, the same proxy works fine with other tools, just puppeteer throws this error.

Using Node 18 + latest puppeteer.

Any fixes or workarounds? Maybe a flag or extra config I'm missing?

Thanks in advance!

(Also, if you've got a better proxy setup for puppeteer, lmk!)

Hey! Had the same puppeteer err_no_supported_proxies issue last week. Turns out, some SOCKS5h proxies just don’t play nice with puppeteer’s internal routing.

Try using a tunneling service like https://www.luminati.io/ or https://oxylabs.io/. They’ve got better compatibility.

Also, double-check your Node version—sometimes downgrading to Node 16 fixes weird proxy bugs.

Ugh, puppeteer and socks5h proxies can be such a pain.

One workaround: Use `proxy-chain` npm package to convert your SOCKS5h to HTTP. Puppeteer handles HTTP proxies way better.

Just wrap your proxy URL like this:
```
const proxyChain = require('proxy-chain');
const newProxyUrl = await proxyChain.anonymizeProxy('socks5h://user:pass@ip:port');
```
Then pass `newProxyUrl` to puppeteer. Works like a charm for me.

Random thought: Are you sure the proxy is alive? Sometimes puppeteer throws err_no_supported_proxies when the proxy is dead or blocking requests.

Test it with `curl --socks5h user:pass@ip:port http://example.com` first.

If it works, maybe puppeteer needs extra args? Try adding `--proxy-server=socks5://ip:port` in `puppeteer.launch()`.

Honestly, puppeteer’s proxy support is hit or miss. I gave up and switched to Playwright for proxy-heavy tasks.

Playwright handles socks5h way better, and the API’s almost identical. Just saying—might save you hours of headache.

If you’re stuck on puppeteer, maybe try a residential proxy? They’re less fussy.

Hey, had this exact puppeteer err_no_supported_proxies issue. Fixed it by ditching socks5h and using a SSH tunnel + local SOCKS5.

1. Set up SSH tunnel: `ssh -D 1080 user@proxy-server`
2. Use `socks5://127.0.0.1:1080` in puppeteer.

No auth headaches, and it’s rock-solid.

Weirdly, I’ve seen puppeteer fail with socks5h but work with socks5. Try stripping the `h` and see if it helps.

Also, check your firewall/AV—sometimes they block puppeteer’s proxy connections silently.

If all else fails, maybe a VPN + puppeteer-stealth could work?

Yo, thanks for all the suggestions!

Tried the `proxy-chain` trick and it kinda worked, but now I’m getting timeouts. Maybe the proxy’s just slow?

Gonna test Playwright like someone suggested—seems easier than fighting puppeteer’s proxy quirks.

Also, SSH tunnel idea is gold. Will def try that next.

Cheers!