Proxies for Puppeteer
Private addresses for browser automation in Puppeteer.
Proxy plans for Puppeteer
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
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
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.
Puppeteer drives a real browser, so the proxy is set the same way it is in Chrome itself, through a launch argument. That brings its own quirk: the address applies to the whole instance rather than to a single tab, so several exits mean several contexts.
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.
The pool hands over private IPv4 by HTTP, HTTPS or SOCKS5, as IP:PORT bound to your address or IP:PORT:LOGIN:PASS. Binding your own IP is the way out here, since the browser launch argument will not carry a login and password pair.
What proxies you need for Puppeteer
| Protocol | HTTP, HTTPS or SOCKS5 |
|---|---|
| How it is set | through the browser launch argument |
| Credentials | not carried in the argument, use binding or a handler |
| Format | IP:PORT or IP:PORT:LOGIN:PASS, access always by binding |
| List refresh | every 15 minutes |
| Authorisation | by binding your own IP in settings, up to 2 addresses |
Setting a proxy in Puppeteer and handling credentials
Almost everyone trips on this one. Two ways out: hand the credentials over separately through a page-level authentication handler, or avoid needing them at all.
The second route usually turns out simpler. Enter your own IP in the dashboard settings and access opens by binding, leaving a bare address and port for the launch argument. You can bind up to two of your own addresses, change them without limits, and activation takes around 5 minutes.
The third place people lose time is name resolution. By default a hostname may be resolved on your own machine, and then the query stays visible to your provider even though the traffic itself goes through the exit. Where that matters, raise the connection in the scheme that has the proxy resolve the name. The same rake lies in Selenium, covered on its own page.
- Chrome ignores credentials inside the launch argument
- Binding your own IP is required anyway and removes the credential question
- The address applies to the browser instance, not the tab
- Several exits mean several contexts or instances
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.
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