PP
Browser Automation

Puppeteer proxy integration

Puppeteer accepts a proxy server via a launch arg, and handles authentication with page.authenticate(). Put the targeting suffix in the username you pass to authenticate(), and the page routes through a residential IP.

Setup steps

  1. 1Install Puppeteer: npm install puppeteer.
  2. 2Launch Chrome with --proxy-server=proxy.aethyn.io:2099.
  3. 3Call page.authenticate() with your username and password.
  4. 4Navigate as usual.

Code

Puppeteer (Node.js)
import puppeteer from "puppeteer";

const browser = await puppeteer.launch({
  args: ["--proxy-server=proxy.aethyn.io:2099"],
});
const page = await browser.newPage();

await page.authenticate({
  username: "aethyn-XXXXX-country-us",
  password: "PASSWORD",
});

await page.goto("https://httpbin.org/ip");
console.log(await page.content());
await browser.close();

Replace aethyn-XXXXX and PASSWORD with your dashboard credentials. See the full targeting reference and protocol/port list. Or use the official proxy-builder-sdk to build targeting strings without hand-assembling usernames.

Tips

  • page.authenticate() must be called before page.goto().
  • One proxy server per browser instance — launch separate browsers for different exits.
  • Combine with puppeteer-extra-plugin-stealth to reduce automation fingerprints.

Puppeteer proxy FAQ

Can each Puppeteer page use a different IP?
Within one browser the proxy server is shared, but rotation still gives fresh IPs per request. For distinct geos, launch a separate browser per proxy configuration.

Ready to wire up Puppeteer?

Get your credentials and route your first Puppeteer request through residential IPs in minutes.

Docs, solutions & blog

Related integrations

All integrations