Puppeteer proxy setup
Configure a NobleProxy dedicated static residential proxy in Puppeteer with the exact fields the app asks for, then run its connection check before real tasks.
Quick answer
Add your NobleProxy host, port, username, and password to Puppeteer's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.
Configure a NobleProxy dedicated static residential proxy in Puppeteer with the exact fields the app asks for, then run its connection check before real tasks.
Add your NobleProxy host, port, username, and password to Puppeteer's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.
| Proxy type / protocol | HTTP or SOCKS5 - both supported on every NobleProxy endpoint |
|---|---|
| Host / endpoint | The host exactly as issued in your NobleProxy dashboard |
| Port | The port paired with your endpoint in the dashboard |
| Username | Your NobleProxy credential (case sensitive) |
| Password | Your NobleProxy credential (case sensitive) |
| Static or rotating | Static - the same exit IP every session by design |
Field labels vary slightly between app versions; the NobleProxy values never change.
Launch the browser with --proxy-server=http://host:port, using the host and port from your NobleProxy dashboard.
Call page.authenticate({ username, password }) with your dashboard credentials so Chromium can answer the proxy's auth challenge.
Open a page that echoes the visitor IP and confirm it shows the endpoint, not your office IP.
Launch one browser instance per proxy so every profile keeps its own stable residential identity.
The tool reports the endpoint IP or country, and target pages load without credential prompts.
A refused connection, timeout, or repeated credential prompt means the host, port, username, or password does not match the dashboard values exactly.
Facts last reviewed 2026-09-01.
Puppeteer passes proxy settings to Chromium as launch arguments, so the browser-level proxy applies to every page in that browser instance. Credentials need page.authenticate because Chromium's --proxy-server argument does not accept a password.
Record which profile uses which endpoint before you start. When every task or profile has one stable residential endpoint, its session history stays consistent across restarts and team handoffs.
NobleProxy endpoints support HTTP and SOCKS5. Pick the protocol Puppeteer asks for in its proxy dialog; both use the same host, port, username, and password.
Use the host, port, username, and password exactly as issued in your NobleProxy dashboard. Enter them in the same fields Puppeteer shows in its proxy configuration screen.
Yes. Map one dedicated static residential proxy to one profile and keep that mapping stable. Reusing the same endpoint for many profiles links their sessions together.
Chromium reports tunnel failures with this exact error.
View pageWhy the same exit IP every run keeps automation stable.
View pageFix the matching proxy error.
View pageAdjacent guide for the same task family.
View pageBuy self-serve now, or talk with us about a larger agency inventory.