How do I configure a proxy in Playwright?

Pass a proxy object when launching the browser: browser.launch({ proxy: { server: "http://gate.birdproxies.com:7777", username: "YOUR_USER", password: "YOUR_PASS" } }). Playwright handles proxy authentication natively - no page.authenticate() call needed like Puppeteer. This works with Chromium, Firefox, and WebKit.

Does Playwright support proxy authentication?

Yes, natively. Unlike Puppeteer which requires page.authenticate(), Playwright accepts username and password directly in the proxy launch config. This makes setup simpler and works consistently across all three browser engines (Chromium, Firefox, WebKit). BirdProxies supports both HTTP and SOCKS5 authentication.

How do I rotate IPs in Playwright?

Create new browser contexts for automatic IP rotation: browser.newContext() with BirdProxies rotating proxies gives you a fresh residential IP per context. For sticky sessions (same IP for multi-page flows), append -session-ID to your username. Each unique session ID maintains the same IP for up to 30 minutes.

Playwright vs Puppeteer for web scraping with proxies?

Playwright has better proxy support - native auth in launch config (no page.authenticate()), multi-browser support (Chromium + Firefox + WebKit), and built-in auto-wait that reduces timing issues. Puppeteer is Chromium-only but has a larger ecosystem of plugins (like stealth). Both work seamlessly with BirdProxies residential proxies.

Can I use different proxies per browser context?

Yes. In Playwright, you can set the proxy at browser level (applies to all contexts) or at context level. For per-context proxies: browser.newContext({ proxy: { server, username, password } }). This lets you run parallel scraping with different IPs and different country endpoints simultaneously.

How do I bypass Cloudflare with Playwright?

Combine BirdProxies residential proxies with Playwright's Firefox or WebKit engines (less fingerprinted than Chromium). Residential IPs pass Cloudflare's ASN-based detection since they come from real ISP ranges. Add proper User-Agent headers and enable JavaScript rendering. For Turnstile challenges, use a CAPTCHA solving service as a fallback.

Does Playwright refresh the page to capture values that change live?

No, Playwright does not reload a page unless your script tells it to. It reloads or navigates only when you call page.reload() or page.goto(), or when the script clicks a link. Reading a value with a locator's inner_text() or with page.evaluate() looks at the DOM of the open tab as it is right now, so checking two tabs every 3 seconds adds no requests of its own. The page keeps up its own background traffic, as it would for any visitor. Keep each tab on one sticky session, because a rotating exit under a live page is what looks odd. On the standard residential plan the dashboard sets a sticky session from 5 minutes up to 1 hour, and when that window ends the exit can change, so a monitor that has to hold one address for days is better off on a static ISP proxy, which keeps the same IP for the whole rental.

Why does Playwright Firefox fail with my PAC proxy when regular Firefox works?

Playwright does not run your installed Firefox. It launches its own patched Firefox build from the ms-playwright cache folder, and to a firewall or endpoint tool that is a different program. NS_ERROR_PROXY_CONNECTION_REFUSED means Firefox picked a proxy and the connection to that proxy was refused. So the PAC file did return a proxy. To test it, hard-code the proxy the PAC returns with launch(proxy={"server": "http://host:port"}) and see whether the error stays; if it does, check whether security software only lets approved executables reach that proxy. A BirdProxies proxy is a plain host and port with a username and password, so there is no PAC file involved.

Why do my residential proxies still get JA3 flagged when the headers look clean?

A proxy does not change your JA3 or TLS fingerprint. An HTTP CONNECT or SOCKS5 proxy relays the encrypted connection without opening it, and the TLS handshake comes from the browser Playwright drives. The target sees the same fingerprint from every exit IP. Headers do not touch it either, because they are sent inside the encrypted connection after the handshake is done. If one pool works on most sites and gets flagged on two, the proxy is probably not the variable on those two. A new pool will not tell you which signal those sites read.

How do I stop Turnstile from breaking my Playwright tests?

Use Cloudflare's dummy Turnstile keys in your test environment instead of the real ones. They work on any domain, localhost included. Sitekey 1x00000000000000000000AA always passes, 2x00000000000000000000AB always fails, and 3x00000000000000000000FF forces an interactive challenge. Pair them with a dummy secret key such as 1x0000000000000000000000000000000AA (always passes server-side validation), because production secret keys reject the dummy token. Then the test checks your form handling and nothing else. A proxy does not fix a test flake.

Will better proxies get my Playwright checkout past a 3DS page?

No, an IP change does not get a script past 3-D Secure. 3DS is the card issuer's own check, and when the issuer asks for it, it wants the cardholder: a password, a one-time code sent to their phone, or a biometric check. Once the challenge is on screen, only the cardholder can complete it, whatever IP the browser uses. More proxy spend buys the same result on the same hop. For testing your own checkout, use your payment provider's test mode; Stripe's testing docs, for example, list cards that always require 3DS authentication.

Is there a web scraping API where the browser part is just handled?

Yes, managed scraping APIs exist, but BirdProxies is not one of them. We sell the IP layer only (residential, ISP and mobile proxies), with no hosted browser and no scraping API. If your mornings go to restarting dead Playwright sessions, a managed API takes that work over and charges per request. Proxies fit when you want to keep your own Playwright code. The sessions are then yours to keep alive.

4.9

Прокси для Playwright без банов IP|

Резидентные прокси с нативной поддержкой прокси в Playwright. Парсинг через Chromium, Firefox и WebKit. Ротация по миллионам реальных IP из 195+ стран.

Работает со всеми популярными инструментами автоматизации

Для автоматизации на Playwright

Что нужно от прокси кроссбраузерному скрипту

Прокси для Playwright

Учётные данные прямо в запуске

Передайте server, username и password прямо в объект proxy при запуске или для каждого контекста, отдельный вызов авторизации потом не нужен.

Отдельный прокси для каждого контекста

Задайте прокси на уровне браузера, чтобы его делили все контексты, или для каждого контекста отдельно, когда параллельным задачам нужны свои адрес и страна.

Один движок, одна настройка прокси

Chromium, Firefox и WebKit принимают один и тот же объект proxy, поэтому смена движка не требует переписывать, как задаётся адрес.

Фиксированные сессии через имя пользователя

Добавьте ID сессии к имени пользователя, чтобы держать один адрес на многостраничном сценарии, или уберите его, чтобы получать новый резидентный IP в каждом контексте.

Для кроссбраузерного парсинга

Что на самом деле помогает запуску Playwright дойти до конца, а не застрять на окне входа

Один адрес на контекст

У каждого контекста браузера свой прокси, поэтому помеченный адрес в одной задаче никогда не задевает остальной параллельный запуск.

Быстро на всех трёх движках

Chromium, Firefox и WebKit одинаково быстро работают через один шлюз, поэтому смена движка никогда не означает смену скорости прокси.

Один контекст постоянно блокируют