+- Proxy Community (https://proxycommunity.com/forum)
+-- Forum: Technical Community Support (https://proxycommunity.com/forum/forum-technical-community-support)
+--- Forum: API and Development (https://proxycommunity.com/forum/forum-api-and-development)
+--- Thread: Getting 'err_no_supported_proxies' with Puppeteer and socks5h Proxy – Any Fixes or Workarounds? (/thread-getting-err-no-supported-proxies-with-puppeteer-and-socks5h-proxy-%E2%80%93-any-fixes-or-workarounds)
Pages:
1
2
Getting 'err_no_supported_proxies' with Puppeteer and socks5h Proxy – Any Fixes or Workarounds? - shadowSurferX - 02-10-2024
Hey folks,
So I’ve been trying to use puppeteer with a socks5h proxy, but I keep running into this error: `err_no_supported_proxies`. It’s driving me nuts!
I’ve double-checked the proxy settings, and everything *seems* correct (lol, typo). The proxy works fine with other tools, but puppeteer just won’t play nice.
Has anyone else dealt with this? I’m wondering if it’s a puppeteer thing or maybe something with the socks5h setup.
Tried a few workarounds like downgrading puppeteer or using a different proxy type, but no luck so far.
Any tips or fixes? Or am I just doomed to keep googling this forever?
Thanks in advance!
“” - ShadowExplorer77 - 05-11-2024
Hey! I had the same issue with puppeteer and socks5h proxies. Turns out, puppeteer doesn’t natively support socks5h proxies out of the box.
What worked for me was using a library like `puppeteer-page-proxy` or `puppeteer-extra-plugin-proxy`. They add proxy support for socks5h and other types.
Here’s a quick example with `puppeteer-page-proxy`:
```javascript
const puppeteer = require('puppeteer');
const useProxy = require('puppeteer-page-proxy');
(async () => {
const browser = await puppeteer.launch();
const page = await browser.newPage();
await useProxy(page, 'socks5h://your-proxy-ip:port');
await page.goto('https://example.com');
await browser.close();
})();
```
Give it a shot and let me know if it works for you!
“” - stealthNomad77 - 31-01-2025
Yo, I feel your pain with the `err_no_supported_proxies` error. Puppeteer can be a bit finicky with proxies, especially socks5h.
One thing you can try is using a tunneling service like `ssh` or `proxychains` to route your traffic through the proxy before it hits puppeteer. It’s a bit of a workaround, but it’s saved me a ton of headaches.
Also, check if your proxy provider supports HTTP proxies. Puppeteer tends to play nicer with those. If you’re stuck with socks5h, though, the `puppeteer-extra` plugin might be your best bet.
“” - ghostVoyX - 08-02-2025
Hey there! I ran into the same `err_no_supported_proxies` issue a while back. After some digging, I found that puppeteer’s proxy support is limited, especially for socks5h.
I ended up switching to a headless browser setup with Playwright instead. It has better proxy support out of the box, including socks5h. If you’re open to trying a different tool, it might be worth a shot.
Here’s a quick example:
```javascript
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch({
proxy: { server: 'socks5h://your-proxy-ip:port' }
});
const page = await browser.newPage();
await page.goto('https://example.com');
await browser.close();
})();
```
Hope this helps!
“” - secureSprintX99 - 19-02-2025
Ugh, the `err_no_supported_proxies` error is the worst. I spent way too much time on this before realizing puppeteer just doesn’t handle socks5h proxies well.
One thing you can try is using a proxy switcher like FoxyProxy or ProxyCap to route your entire system traffic through the socks5h proxy. Then, puppeteer will just use your system’s proxy settings. It’s not ideal, but it works in a pinch.
Alternatively, you could try using a VPN with a socks5h proxy endpoint. It’s a bit overkill, but it might save you some time.
“” - shadowSurferX - 23-02-2025
Wow, thanks for all the suggestions, everyone! I didn’t expect so many helpful replies.
I tried the `puppeteer-extra` plugin with the proxy setup, and it worked like a charm! No more `err_no_supported_proxies` errors.
I also tested the `tinyproxy` workaround, and it’s a solid backup plan if I ever need it.
Quick question though—has anyone tried using multiple socks5h proxies with puppeteer? I’m thinking of rotating proxies for a scraping project, and I’m not sure if the `puppeteer-extra` plugin supports that.
Thanks again, you guys are awesome!
“” - IPNinja33 - 03-03-2025
Hey! I’ve been down the puppeteer and socks5h rabbit hole before. The `err_no_supported_proxies` error usually pops up because puppeteer doesn’t have built-in support for socks5h proxies.
I’d recommend checking out the `puppeteer-extra` package. It’s a drop-in replacement for puppeteer with extra plugins, including one for proxy support. Here’s how you can set it up:
```javascript
const puppeteer = require('puppeteer-extra');
const pluginProxy = require('puppeteer-extra-plugin-proxy');
puppeteer.use(pluginProxy({
socks5h: 'your-proxy-ip:port'
}));
(async () => {
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.com');
await browser.close();
})();
```
Give it a try and see if it resolves your issue!
“” - maskedVoyX99 - 07-03-2025
Oh man, the `err_no_supported_proxies` error is such a pain. I’ve been there with puppeteer and socks5h proxies.
One thing that worked for me was using a local proxy server like `tinyproxy` or `squid` to convert the socks5h proxy into an HTTP proxy. Puppeteer handles HTTP proxies much better, so it might be worth a shot.
Here’s a quick setup guide for `tinyproxy`:
1. Install tinyproxy: `sudo apt-get install tinyproxy`
2. Edit the config file to forward traffic to your socks5h proxy.
3. Point puppeteer to the local HTTP proxy.
It’s a bit of a hack, but it got the job done for me.
“” - stealthDash77 - 10-03-2025
Hey! I’ve been using puppeteer with socks5h proxies for a while, and the `err_no_supported_proxies` error is a common headache.
One thing you might want to check is whether your proxy provider supports DNS resolution over socks5h. If not, puppeteer might be failing to resolve the hostnames, which could trigger the error.
You can test this by using a tool like `curl` with the `--socks5-hostname` flag to see if the proxy works outside of puppeteer. If it does, then the issue is likely with puppeteer’s proxy handling.
In that case, I’d second the recommendation to use `puppeteer-extra` with the proxy plugin. It’s been a lifesaver for me.