Puppeteer

This page covers Puppeteer proxy setup, including authenticated proxies. Puppeteer launches Chrome/Chromium, so a ColdProxy gateway connects through the --proxy-server launch argument, and Puppeteer's page.authenticate() supplies the username and password. The key thing to know: page.authenticate() answers HTTP/HTTPS proxy auth only; SOCKS5 username/password is a browser-level gap, so use IP authentication (or an upstream helper) for SOCKS5. Below are rotating and sticky setups, plus the puppeteer-extra variant. For background, see IP whitelisting vs username/password.

#Your ColdProxy connection details

Proxy server: gw-2312.coldproxy.com:30000
Username:     USERNAME     (may carry geo/session tags — see below)
Password:     PASSWORD

2312 is your service/package ID from the client area; 30000 is any port in your plan's 30000-34999 allocation. Residential IPv4 (GB Based) and Residential IPv6 activate instantly after payment clears; Residential IPv4 (Unmetered) and Datacenter IPv6 start automatic setup after payment clears. Allow up to 10 minutes for those two plans and connect as soon as setup completes. See Activation and setup times, then verify with the proxy checker and my IP.

#Set the proxy and authenticate with page.authenticate()

Pass the gateway on --proxy-server, then call page.authenticate() with your credentials before the first navigation. Chrome will not accept user:pass@host inside --proxy-server, which is exactly why page.authenticate() exists.

const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch({
    args: ['--proxy-server=gw-2312.coldproxy.com:30000'],
  });
  const page = await browser.newPage();

  await page.authenticate({ username: 'USERNAME', password: 'PASSWORD' });

  await page.goto('https://api.vipv6proxy.com/api/checker/my-ip', { waitUntil: 'domcontentloaded' });
  console.log(await page.evaluate(() => document.body.innerText));
  await browser.close();
})();

#Rotating across pages and contexts

The proxy is fixed at launch, so to use several ColdProxy exits at once, launch one browser per configuration or use isolated browser contexts and authenticate each page. The exit behavior is controlled by the tagged username you pass to page.authenticate(), not by the port.

const puppeteer = require('puppeteer');

async function withProxy(username) {
  const browser = await puppeteer.launch({
    args: ['--proxy-server=gw-2312.coldproxy.com:30000'],
  });
  const page = await browser.newPage();
  await page.authenticate({ username, password: 'PASSWORD' });
  await page.goto('https://api.vipv6proxy.com/api/checker/my-ip');
  const body = await page.evaluate(() => document.body.innerText); // JSON: {ip, country, ...}
  await browser.close();
  return body;
}

(async () => {
  console.log(await withProxy('USERNAME')); // rotating
  console.log(await withProxy('user-country-us-session-481516-time-10m')); // sticky US
})();

#Geo-targeting and sticky sessions through the username

ColdProxy encodes geo and session controls as tags inside the username, grammar user-key-value-key-value... (full reference: Username tag scheme). Rotation is the default; a sticky IP needs both a session id and a duration together. The tagged username goes straight into page.authenticate(). See rotating and sticky proxies and geo-targeting with proxies.

// Rotating, United States — new IP per request
await page.authenticate({ username: 'user-country-us', password: 'PASSWORD' });

// Sticky 10 minutes, United States — same IP while the session holds
await page.authenticate({
  username: 'user-country-us-session-481516-time-10m',
  password: 'PASSWORD',
});

#IP whitelisting (no credentials — and the SOCKS5 path)

ColdProxy supports IP authentication: whitelist up to 50 IPs in the client area or the plan API, and skip page.authenticate() entirely.

const browser = await puppeteer.launch({
  args: ['--proxy-server=gw-2312.coldproxy.com:30000'],
});
// No page.authenticate() needed — this machine's IP is whitelisted

For SOCKS5, IP whitelisting is the way to authenticate, because Chrome cannot do SOCKS5 user:pass:

const browser = await puppeteer.launch({
  args: ['--proxy-server=socks5://gw-2312.coldproxy.com:30000'],
});

#puppeteer-extra and stealth

If you already run puppeteer-extra with the stealth plugin in a legitimate, authorized workflow, proxy setup is identical; the launch arg and page.authenticate() behave the same:

const puppeteer = require('puppeteer-extra');
const StealthPlugin = require('puppeteer-extra-plugin-stealth');
puppeteer.use(StealthPlugin());

const browser = await puppeteer.launch({
  args: ['--proxy-server=gw-2312.coldproxy.com:30000'],
});
const page = await browser.newPage();
await page.authenticate({ username: 'USERNAME', password: 'PASSWORD' });

#Verify and troubleshoot

• Read document.body.innerText after loading https://api.vipv6proxy.com/api/checker/my-ip, or run the proxy checker, to confirm the exit IP and location.
• If pages load but show your real IP, page.authenticate() likely ran after goto; move it before the first navigation.
• net::ERR_PROXY_CONNECTION_FAILED right after ordering can have several causes. Check your settings and service status. If you bought Residential IPv4 (Unmetered) or Datacenter IPv6, automatic setup may still be running for up to 10 minutes after payment clears; see Activation and setup times.
• A SOCKS5 launch that ignores the proxy is the Chrome SOCKS5-auth gap; switch to IP whitelisting or the proxy-chain upstream.
• For IPv6 plans, check the target with the IPv6 checker before buying: it should publish an AAAA record or be served by a supported CDN (see IPv6 reachability). Confirmed IPv6-ready platforms include Google, YouTube, Facebook, Instagram, Bing, and LinkedIn.

Ready to provision? Compare plans on pricing or browse the proxy products.