PiratProxies

Web scraping

Proxies in Puppeteer: working examples

Puppeteer drives Chrome from Node.js. The proxy address goes in a launch argument, and the username and password are given to the page.

The right proxy type for Puppeteer

For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.

The values to enter in Puppeteer

Every PiratProxies plan comes down to four values: host, port, username and password. Here they are for Residential; your own username and password are on your plan page.

Hostresi.piratproxies.com
HTTP port8080
SOCKS5 port1080
UsernameUSERNAME
Passwordshown on your plan page

There is no separate country or session field: both are part of the username. Your plan page has a generator that writes it, and Targeting and sessions describes each piece.

Setting it up in Puppeteer

  1. Launch Chrome with --proxy-server and the host and port only.
  2. Call page.authenticate with the username and password before the first navigation.

Code: Puppeteer through a proxy

Node.js

const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch({ args: ['--proxy-server=http://resi.piratproxies.com:8080'] });
  const page = await browser.newPage();
  await page.authenticate({ username: 'USERNAME', password: 'PASSWORD' });
  await page.goto('https://api.ipify.org');
  console.log(await page.evaluate(() => document.body.innerText));
  await browser.close();
})();

Put your own login from the plan page in place of USERNAME and PASSWORD. The example calls an IP-check service, so what it prints is the address your request came from.

Should Puppeteer rotate IPs or keep one?

When Puppeteer is fetching lots of unrelated pages, leave the session out of the username and each request gets a fresh IP address. When requests belong together, such as a login, a basket or paginated results that set cookies, put a session in the username so they all share one address.

Here is what a sticky username looks like:

USERNAME-country-us-time-600-session-a1b2c3d4

When Puppeteer will not connect

  • page.authenticate is per page. Call it on every new page, or that page gets a 407.
  • One browser has one proxy. For several IP addresses at once, launch several browsers or use browser contexts with a proxy per context.
  • Error 407 means the login was refused. Copy the username and password from your plan page once more, and make sure no space crept in and the username was not cut short.
  • An IP in the wrong country nearly always comes from the username, since the country code lives there. Other fixes.

Puppeteer and proxies: questions

Can Puppeteer use a SOCKS5 proxy?

Only without a login: Puppeteer cannot send a SOCKS5 username and password. Use the HTTP port, 8080, instead; it handles http and https sites alike.

Which PiratProxies plan suits Puppeteer best?

For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.

Words used in this guide: web scraping, rotating proxy, sticky session, rate limiting, headless browser.

Puppeteer belongs to its own developers, and PiratProxies has no connection with them; we name it only to say what this guide covers. Follow the rules of the sites you visit and our acceptable use policy.