Give Playwright one static ISP address, at launch or for a single browser context. The samples were run in Chromium, Firefox and WebKit against a local proxy before they were published.
In short: Pass proxy with server, username and password to chromium.launch, or to browser.new_context to scope it to one context. Over HTTP, all three engines authenticate with those fields. Over SOCKS5 none of them accepts a username and password: Playwright refuses to launch. Put your IP on the proxy’s whitelist and give only the socks5:// server.
Playwright drives Chromium, Firefox and WebKit through one API, and the proxy is part of how a browser or a context is created. That makes it easy to run several addresses in one script, and it is also where its one hard limit sits: SOCKS5 with a password.
The Python sample launches Chromium with the proxy for the whole browser; the per-context sample scopes it to one context instead. Switching the engine is changing chromium to firefox or webkit; the proxy object stays the same.
The three engines answer the proxy’s 407 with the username and password from the proxy object when the proxy speaks HTTP. A SOCKS5 proxy gets no such answer from any of them, which is why the SOCKS5 sample carries no credentials and relies on the whitelist.
A proxy cannot be attached to a single page. The unit is the context: create one context per address and open the pages that should share that address inside it. Contexts are cheap in Playwright, so a script that checks one storefront from three countries holds three contexts, each built from its own order.
The proxy object also takes a bypass field, a comma-separated list of hosts that should be reached directly. Use it for your own internal services or a local test server, so that only the traffic meant for the outside world leaves through the address you pay for.
From My Proxies in the dashboard or the order in the API. Every address comes with its own four values.
At launch the whole browser uses the proxy. On new_context only that context does, so one script can run several contexts through different addresses.
{"server": "http://HOST:PORT", "username": "USERNAME", "password": "PASSWORD"}. The credentials go in their own fields, never inside the server URL.
Playwright cannot log in to a SOCKS5 proxy, so switch the order to SOCKS5, admit your machine’s IP with the whitelist call in the code tabs, and keep only socks5://HOST:PORT, using the new port. While a whitelist is set, the proxy admits only the listed addresses and the username and password stop working for that order; sending an empty list turns the whitelist off and password login works again.
Open What Is My IP in a page of that browser or context once, before the real run.
# pip install playwright && playwright install chromium
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(proxy={
"server": "http://HOST:PORT",
"username": "USERNAME",
"password": "PASSWORD",
})
page = browser.new_page()
page.goto("https://example.com/")
print(page.title())
browser.close()
// npm i playwright && npx playwright install chromium
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch({
proxy: {
server: 'http://HOST:PORT',
username: 'USERNAME',
password: 'PASSWORD',
},
});
const page = await browser.newPage();
await page.goto('https://example.com/');
console.log(await page.title());
await browser.close();
})();
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch()
# The proxy belongs to this context only; another context can use
# a different address, or none.
context = browser.new_context(proxy={
"server": "http://HOST:PORT",
"username": "USERNAME",
"password": "PASSWORD",
})
page = context.new_page()
page.goto("https://example.com/")
print(page.title())
browser.close()
# Switch the proxy to SOCKS5 and put your machine's IP on its whitelist:
# Chromium cannot send a SOCKS5 username and password.
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(proxy={"server": "socks5://HOST:PORT"})
page = browser.new_page()
page.goto("https://example.com/")
print(page.title())
browser.close()
# Put the public IPv4 address your code runs from on the proxy's
# whitelist. Replaces the list; an empty list turns whitelisting off
# and the proxy falls back to username and password.
curl -X PUT "https://api.proxyjam.com/public/v1/orders/ORDER_ID/whitelist" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"whitelisted_ips": ["YOUR_IP"]}'
Run with Playwright 1.64 for Python and for Node. The HTTP samples send a username and password and need an order with no whitelist set; the SOCKS5 one relies on the whitelist and needs the proxy switched to SOCKS5 first, which gives a new port. Replace the capitals with your order's values.
| HTTP with password | SOCKS5 with password | SOCKS5, whitelisted | |
|---|---|---|---|
| Chromium | Works | Refused at launch | Works |
| Firefox | Works | Refused at launch | Works |
| WebKit | Works | Refused at launch | Works |
Playwright reads the username and password from their own fields. Written into the server URL instead, they are not sent at all: in our test the first navigation hung until it timed out, with no message that pointed at the credentials.
Every engine refuses SOCKS5 authentication, and the error arrives at launch, before any page opens. The fix is not a different library: whitelist the IP your script runs from and drop the credentials.
Pages share the proxy of their context, and contexts share the browser's unless given their own. To run two addresses side by side, create two contexts, each with its proxy.
A typo in the port or a proxy still set to HTTP fails loudly, but a context created without the proxy object goes out directly and silently. Load an IP echo page once per context you configure.
One context, one address
HTTP sign-in
SOCKS5 sign-in
Stability
Pass an object with server, username and password, either to launch or to new_context. Over an HTTP proxy, Chromium, Firefox and WebKit all send those credentials when the proxy asks for them.
No. Playwright stops at launch with an error saying the browser does not support SOCKS5 proxy authentication, in all three engines. Whitelist the IP your script runs from, then pass only the socks5 server; our whitelist applies over SOCKS5 as well as HTTP. SOCKS5
Give each browser context its own proxy and open the page in that context. Pages inside one context always share its proxy, so per-page proxies mean one context per page.
The same object with the same three fields: Python writes it as a dictionary, Node as an object literal. Both samples on this page were run with Playwright 1.64.
Testing your own pages by region, quality checks, ad verification, price and market research, SEO monitoring and brand protection run without prior review under our acceptable use policy. Public availability alone does not authorise collecting data, personal data needs a stated lawful basis, and the address does not get past CAPTCHAs, bot detection, rate limits or bans; the policy forbids trying. Acceptable Use Policy
