---
Hey y'all,
So I've been banging my head against the wall with this *puppeteer err_no_supported_proxies 'socks5h'* error. Like, seriously, what even is this? I’m trying to run Puppeteer with a SOCKS5 proxy, and it just keeps throwing this nonsense at me.
From what I’ve gathered, Puppeteer doesn’t natively support 'socks5h' out of the box. Ugh, why tho? I tried switching to 'socks5' instead, and it kinda worked, but not always. Some folks suggested using a wrapper like `socks-proxy-agent`, but honestly, that feels like adding more steps to an already annoying process.
Anyone else dealt with this? Did you find a clean workaround, or is it just a lost cause? I’m tempted to just ditch Puppeteer altogether at this point, but I’m too deep in the code to quit now.
Pls help a dev out before I lose my mind.
---
Hey! I feel your pain with the puppeteer err_no_supported_proxies 'socks5h' error. It’s such a headache, right? I ran into this a while back and ended up using `socks-proxy-agent` as a workaround. Yeah, it’s an extra step, but it’s pretty straightforward once you set it up.
Here’s a quick snippet that worked for me:
```javascript
const SocksProxyAgent = require('socks-proxy-agent');
const agent = new SocksProxyAgent('socks5://your-proxy-address:port');
const browser = await puppeteer.launch({ args: ['--proxy-server=${agent.proxy.host}:${agent.proxy.port}'] });
```
Give it a shot and lmk if it helps!
Ugh, the puppeteer err_no_supported_proxies 'socks5h' error is the worst. I had the same issue and switched to using `puppeteer-extra` with the `puppeteer-extra-plugin-proxy` plugin. It’s a bit more flexible and handles SOCKS5 proxies way better.
You can install it via npm:
```bash
npm install puppeteer-extra puppeteer-extra-plugin-proxy
```
Then configure it like this:
```javascript
const puppeteer = require('puppeteer-extra');
const ProxyPlugin = require('puppeteer-extra-plugin-proxy');
puppeteer.use(ProxyPlugin({ socks5: 'your-proxy-address:port' }));
```
Hope this saves you some time!
Man, I feel you. That puppeteer err_no_supported_proxies 'socks5h' error is a nightmare. I ended up ditching Puppeteer for Playwright for this exact reason. Playwright has native SOCKS5 support, and it’s been way smoother for me.
If you’re open to switching, here’s how you can set it up:
```javascript
const { chromium } = require('playwright');
const browser = await chromium.launch({ proxy: { server: 'socks5://your-proxy-address:port' } });
```
It’s worth a shot if Puppeteer keeps giving you trouble.
Hey! I had the same puppeteer err_no_supported_proxies 'socks5h' issue, and it drove me nuts. I found a workaround by using a local proxy server like `ssh -D` to tunnel traffic through SOCKS5.
Here’s what I did:
1. Set up an SSH tunnel:
```bash
ssh -D 1080 user@your-server
```
2. Point Puppeteer to the local proxy:
```javascript
const browser = await puppeteer.launch({ args: ['--proxy-server=socks5://127.0.0.1:1080'] });
```
It’s a bit hacky, but it worked for me. Good luck!
Thanks, everyone! I tried the `socks-proxy-agent` solution, and it worked like a charm. Still a bit annoyed that Puppeteer doesn’t natively support 'socks5h', but hey, at least there’s a workaround.
I also checked out Playwright, and it looks promising. Might switch over if I run into more issues.
Quick question though—anyone know if there’s a way to make Puppeteer handle 'socks5h' without extra libraries? Or is that just wishful thinking?
