Proxies for Puppeteer
Private addresses for browser automation in Puppeteer.
Proxy plans
Every plan includes IPv4 and SOCKS5 together, at no extra cost.
Threads are simultaneous connections. The more threads, the higher the parallel load your software can handle.
Pool of 12,000-15,000 IPs
Address rotation
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Up to 3,000 threads
Proxy catalog for your task
Why Puppeteer needs proxies
Puppeteer drives a headless Chromium browser for automation and scraping. Parallel instances from one address quickly hit captchas and limits.
A pool of private addresses gives instances different IPs, and collection runs smoothly on volume. The more parallel pages, the more a set of addresses is needed.
Features of proxies for Puppeteer
Puppeteer drives headless Chrome from Node.js, and when launching many pages each instance must run from its own address. Otherwise the site links automated sessions by IP.
Our pool provides private IPv4 and SOCKS5, IP:PORT format. For mass launch you take rotation, for tied scenarios an address from the pool.
What proxies you need for Puppeteer
| Protocol | HTTP, HTTPS or SOCKS5 |
|---|---|
| Threads | matching parallel browsers |
| Addresses | private IPv4 with rotation |
| Format | IP:PORT (main) or IP:PORT:LOGIN:PASS |
| Where to add | launch args, auth via page.authenticate |
| Authorization | by binding your IP in the settings, up to 2 |
How to connect proxies in Puppeteer
To make the pool work, bind the IP of the machine running your proxy software in the settings, a server or a home PC, no binding means no access. The primary output format is IP:PORT, with an additional IP:PORT:LOGIN:PASS for programs that require a login and password.
In Puppeteer the proxy is passed in args at launch (--proxy-server=IP:PORT), with authorization via page.authenticate. Format IP:PORT, HTTP or SOCKS5.
The setup is checked on a couple of instances. How many addresses you need for your parallel browser count is visible on the free test.
How to buy proxies for Puppeteer
The process is simple. Register in the dashboard and request a free test up to 2 hours, bind your IP and message the operator in a ticket to check the setup with Puppeteer on your own tasks.
When everything fits, pick a package by number of threads and term, pay in cryptocurrency, and access opens right after payment. The test is provided once before purchase, and support replies in a ticket.
FAQ
Will these proxies work with Puppeteer?
Puppeteer accepts a proxy via a launch argument in HTTP, HTTPS and SOCKS5, with authorization through page.authenticate. The fit is visible on the free test.
How many instances can I run?
The number of parallel instances and bindings depends on the package, and the pool of 12,000-15,000 IPv4 gives sessions different addresses.
Which protocol should I choose, HTTP or SOCKS5?
For most Puppeteer scenarios both fit; SOCKS5 is handier for non-standard connections. Both can be checked on the test.
How much do proxies for Puppeteer cost?
The price depends on the number of threads and the package term; current plans are in the block above on this page. A free test up to 2 hours is available before payment.
See also: buy proxies for BAS, buy proxies for Selenium, buy proxies for Python scripts, buy proxies for ZennoPoster, buy proxies for AMS Enterprise, buy proxies for A-Parser, buy proxies for AI, buy proxies for ChatGPT, full catalog
© WinGate · source of the material · wingate.me/en/proxy/puppeteer-proxy