Playwright proxy setup that survives production
Scripts written with Playwright rarely break on selectors. They break on the network: after a few hundred page loads the target starts returning captchas, empty HTML or 403s, and the dataset arrives half-collected. Routing the same script through an IP of a real mobile carrier changes that arithmetic — requests arrive as ordinary phone traffic, so pages come back parsed instead of blocked, and the budget goes into a port rather than into retries.
Two decisions define everything else: the protocol used for the connection and the type of IP behind it. A playwright proxy on a datacenter range is cheap and fast, and it is also the first thing flagged; carrier IPs carry the highest trust score of all proxy types, because blocking one of them would hit thousands of real subscribers sharing it. Choosing a playwright proxy server this way is not a technical detail — it is the difference between a job that finishes overnight and a job you babysit.
How to connect a playwright socks5 proxy in code
Playwright accepts a proxy at two levels, and both are one line. At launch: proxy: { server: "socks5://host:port" } inside the async launch options, after which every page in that browser leaves through the same exit. Per context: browser.newContext({ proxy: { ... } }), which is the mode that matters for account work, because each profile gets its own IP and one flagged session no longer drags the whole farm down.
Per-context assignment is also the cheapest way to scale a crawler. Spin up several async workers, bind each one to a separate port, and the run time drops proportionally without a single change to the parsing logic. Keep the port list in configuration instead of hardcoding it — swapping a country or a carrier then takes a minute, not a refactor.
The username and password trap in Chromium
Here is the detail that costs people an evening of debugging: Chromium does not implement SOCKS5 authentication, so the username and password inside a socks5:// URL are silently ignored. The config looks correct, the script runs, and requests either fail or leave from the machine's real address. Two methods work reliably instead — connect over socks5 with the runner's IP whitelisted, or keep login:password authentication and switch the scheme to http://.
OnlineProxy ports answer on both protocols and support both authentication methods, so the choice depends on where the code lives rather than on what the provider allows. Static server with a fixed address — whitelist and use SOCKS5, including its UDP support for WebRTC checks. Cloud runners with a new address on every start — credentials over HTTP, no re-registration each time.
| Connection | Authentication | Chromium result | Best for |
|---|
| socks5:// + whitelist | No credentials in code | Works | Static runners, UDP tasks |
| socks5:// + username:password | In launch options | Ignored, silent leak risk | Avoid |
| http:// + username:password | In launch options | Works | Dynamic or cloud IPs |
| Per-context proxy | Either method | Works | One account per port |
Pro-tip: after the first successful launch, open an IP-check page inside the same context and log the ASN and fraud score. A carrier ASN with a low score means the setup is live; a hosting ASN means the traffic bypassed the proxy entirely — and catching that in the first minute saves the accounts you were about to warm up.
Rotation: match the IP lifetime to the job
A parser and an account farm need opposite behavior from the same port. Long sequences — login, cart, checkout, paginated crawling — need a sticky session, otherwise the target sees the identity change mid-flow. Mass collection of independent URLs benefits from frequent change, because rate limits reset with every new address.
On a Regular port both are under your control: hold the IP as long as needed, force a new one with a link request at the exact moment the script decides, or set timer rotation for jobs that run unattended overnight. Link rotation is the one worth wiring into the code — one HTTP call inside the retry branch, and a soft block turns into a two-second pause instead of a dead worker.
Concurrency limits nobody mentions
One mobile device handles roughly one to five parallel streams comfortably. Thirty headless contexts pointed at a single port will not get banned — they will get slow, time out, and produce empty pages that look exactly like detection. Latency on a carrier network sits in the 50–300 ms range by nature, so timeouts in Playwright deserve a higher value than the defaults tuned for wired links.
The practical planning method: decide the number of simultaneous contexts first, divide by three, and rent that many ports. Traffic is not metered on either plan, so throughput per port is the only variable to size — no surprise invoice after a heavy crawl of image-rich pages.
What a mobile IP does not fix
Network legitimacy is one layer of four. A headless browser still exposes a fingerprint, and default automation flags survive any proxy, so account scenarios pair the port with an antidetect browser and one profile per port. Playwright itself covers the behavioral layer if the script is written for it: randomized delays, real scrolling, no three-page-per-second bursts.
Geo consistency is the cheapest win of the three. Locale, timezone and viewport set in the context options must agree with the country and carrier of the rented port — a Warsaw IP with a New York timezone is an instant red flag, and fixing it costs two lines of configuration. Get those four elements aligned and success rates on aggressive targets move from under 80% to the 95–99% range.
Ports, plans and what happens when something breaks
Billing is per port for a period — 1, 7 or 30 days, with 24 hours as the minimum term — and never per gigabyte. Prices depend on the country and the carrier and are shown on the plan page, so a heavy scraping month and a light one cost the same. Predictable cost per worker makes capacity planning a spreadsheet exercise rather than a gamble.
| Plan | Device access | IP control | Fits |
|---|
| Lite | Shared, up to 5 users | Auto rotation every 2–5 min | Stateless crawling, checks |
| Regular | Dedicated for the term | Sticky, link, timer, reboot | Accounts, long sessions |
For account work and any flow that must hold state, a playwright socks5 proxy belongs on a Regular port — a shared device rotating on its own schedule will drop a session in the middle of a login. Lite covers the opposite case well: independent requests where a new address every few minutes is a feature, not a problem. Support answers around the clock with a target first reply of four hours, and Regular ports get priority in the queue.
Before renting anything, a single free server proxy is available through the widget on the site — enough to verify that the launch options, authentication and async workers behave as expected. Mobile ports are paid, with no free trial on them; what does soften the risk is cashback in promo credits on the internal balance after a completed rental, plus the refund and replacement policy: a full refund within the first hour after access is issued, later minus the time used, and a replacement port offered first when the issue is technical. Test the code for free, then pay only for the carrier IPs that actually carry your jobs.
