Use RoProxy with Playwright

Use the HTTP port

Chromium does not send a username and password to SOCKS5 proxies: it drops the credentials, the proxy refuses the connection, and the page fails or leaves without the proxy. RoProxy sessions always authenticate, so point Chromium at the session's HTTP port.

HTTPS sites work through that port: the browser opens a CONNECT tunnel and TLS stays between the browser and the site.

One proxy for the whole browser

import { chromium } from "playwright"

const browser = await chromium.launch({
  proxy: {
    server: "http://GATEWAY_HOST:HTTP_PORT",
    username: "USERNAME",
    password: "PASSWORD",
  },
})
const page = await browser.newPage()
await page.goto("https://api.ipify.org?format=json")
console.log(await page.textContent("body"))
await browser.close()

from playwright.sync_api import sync_playwright

with sync_playwright() as p:
    browser = p.chromium.launch(proxy={
        "server": "http://GATEWAY_HOST:HTTP_PORT",
        "username": "USERNAME",
        "password": "PASSWORD",
    })
    page = browser.new_page()
    page.goto("https://api.ipify.org?format=json")
    print(page.text_content("body"))
    browser.close()

One session per context for parallel IPs

A browser context is an isolated profile with its own cookies. Give each context its own session and one browser runs several IPs side by side.

import { chromium } from "playwright"

// Each entry is one RoProxy session, copied from the dashboard.
const sessions = [
  { server: "http://GATEWAY_HOST:HTTP_PORT", username: "USERNAME_1", password: "PASSWORD_1" },
  { server: "http://GATEWAY_HOST:HTTP_PORT", username: "USERNAME_2", password: "PASSWORD_2" },
]

const browser = await chromium.launch()
await Promise.all(sessions.map(async (proxy) => {
  const context = await browser.newContext({ proxy })
  const page = await context.newPage()
  await page.goto("https://api.ipify.org?format=json")
  console.log(await page.textContent("body"))
  await context.close()
}))
await browser.close()

Choosing the session type for a browser

• Sticky (bind)

  The default choice for browsers: logins, carts and multi-step flows keep one IP and one cookie jar.

• Timed rotation

  Good for crawling many pages in a row, as long as no login spans the moment the IP changes.

• Per request (Business)

  A page loads dozens of resources and each could leave from a different IP, which some sites flag. Better for API-style fetches than for full page loads.

Common errors

• net::ERR_TUNNEL_CONNECTION_FAILED

  The gateway host or port is wrong, or the session has expired. Check the connection string in the dashboard.

• 407 or a proxy login prompt

  The username or password is missing or wrong. Pass both in the proxy option, not in the server URL.

• Slow page loads

  Every resource goes through the proxy. Block images, fonts and media with page.route when you only need the HTML.