Puppeteer proxy setup

Protocols

HTTP proxy on port 7000 (HTTPS sites through CONNECT). Chrome has no SOCKS5 login

Authentication

page.authenticate() before the first goto; one login per browser context

Rotation

A sticky -sid- login: one IP per browser or per context, for up to 60 minutes

Works with

Residential and mobile proxies

Before you start

• Node.js 22.12 or newer and npm i puppeteer, which downloads its own Chrome for Testing.
• Your proxy login and password from the Residential or Mobile page of the dashboard.
• Traffic on the product you use: a login without traffic gets 402.

One proxy for the browser

Give Chrome the address with --proxy-server, then the login with page.authenticate() before the first goto. Chrome ignores a login written into the flag.

import puppeteer from "puppeteer";

const browser = await puppeteer.launch({
  args: ["--proxy-server=http://gate.aeonproxy.com:7000"],
});
const page = await browser.newPage();
await page.authenticate({ username: "LOGIN-cc-us-sid-ab12cd34-ttl-30", password: "PASSWORD" });
await page.goto("https://api.ipify.org");
console.log(await page.$eval("body", (el) => el.innerText));
await browser.close();

Chrome keeps the first proxy login that worked and sends it for every later page of the same browser context, popups included. In our test a second page with its own authenticate() and another key still went out with the first key, so use one key per context and a new context for a new key. authenticate() turns on request interception behind the scenes, which Puppeteer's docs say may cost some speed.

A proxy per browser context

createBrowserContext({ proxyServer }) gives each context its own proxy and cookies, so each can have its own country and sticky IP.

import { randomBytes } from "node:crypto";
import puppeteer from "puppeteer";

const browser = await puppeteer.launch();
for (const country of ["us", "de", "jp"]) {
  const context = await browser.createBrowserContext({ proxyServer: "http://gate.aeonproxy.com:7000" });
  const page = await context.newPage();
  const sid = randomBytes(4).toString("hex");
  await page.authenticate({ username: `LOGIN-cc-${country}-sid-${sid}-ttl-30`, password: "PASSWORD" });
  await page.goto("https://api.ipify.org");
  console.log(country, await page.$eval("body", (el) => el.innerText));
  await context.close();
}
await browser.close();

SOCKS5

Chrome supports no login for SOCKS5 proxies, and page.authenticate() does not change that: with --proxy-server=socks5://gate.aeonproxy.com:7001 pages fail with net::ERR_SOCKS_CONNECTION_FAILED. Use the HTTP port 7000.

Rotating or sticky

One page opens many connections, and a rotating login gives each of them a new IP. Use a sticky login as in the examples, and a new context with a new key when you need a new IP. To check the exit, open IP checker in the page.

If it does not work