Puppeteer Proxy Setup for Node Browser Automation

Use this Puppeteer proxy guide to run Chromium through Proxy Grove from Node.js. Lawful automation only. Prefer clear env-based config and one proxy label per job type.

Proxy Grove Unlimited plans: Residential/Corporate from $2/IP/day, Mobile from $4.50/IP/day, HTTP/SOCKS5, sticky or rotating. See pricing.

Launch configuration

Pass --proxy-server= in puppeteer.launch args. Keep headless policy consistent between staging and production so you do not debug “proxy bugs” that are actually headful differences. Freeze Chromium revisions in CI.

Sticky vs rotating

Multi-step flows need sticky endpoints. Discovery crawls can use rotating. Configure mode in Proxy Grove; Puppeteer should stay dumb about pool internals. Do not rotate page-by-page unless the plan is meant to rotate.

Concurrency and memory

Chromium tabs are expensive. Cap pages per process and processes per sticky IP. Rotate browser processes on memory thresholds, not on every request. Track RSS and event-loop lag alongside block rates.

Observability

Log navigation URL, proxy label, and exit IP check. Screenshot on navigation failure. Without logs, teams randomly rewrite proxy strings. Correlate with auth failures separately from target blocks.

Puppeteer vs Playwright

Playwright is usually better for new multi-browser fleets. Puppeteer remains fine for Chromium-only Node apps already in production. See Playwright and Selenium guides for alternatives.

Docker and Chromium dependencies

Container images must include the libraries Chromium expects. Proxy misconfiguration and missing shared libraries produce similar browser failed to launch symptoms. Separate health checks: local launch without proxy, then launch with proxy to a canary.

Request interception

If you abort image loads to save bandwidth on a GB meter, document that choice because your visual QA will be wrong. On per-IP Unlimited plans, aborting images is an accuracy decision, not a cost decision. Align product and engineering before enabling interception.

Next steps on Proxy Grove

Compare live Unlimited pricing, open residential, mobile, or corporate, then create endpoints in the app. For protocol choice read SOCKS5 vs HTTP. For meter math read unlimited vs pay-per-GB.