How to set up your Mobile Proxy in browser automation tools

Once you activate your dedicated Mobile Proxy, you get four pieces of information: host, port, protocol (SOCKS5 or HTTP), and credentials (username and password). This guide shows how to plug each one into the browser automation tools most commonly used by QA and dev teams.

Before you start, grab your proxy's details from the "My Proxies" section of your dashboard — there's a copy button next to each field.

Puppeteer

Puppeteer takes the proxy as a browser launch argument, and authentication is handled separately via `page.authenticate()`:

• Launch the browser passing `--proxy-server=protocol://host:port` in `args` (e.g. `--proxy-server=socks5://your-host:your-port`).
• Open a new page and call `page.authenticate({ username: 'your-username', password: 'your-password' })` before navigating.
• Confirm the connection by navigating to an IP-check page and comparing the address to the one in your dashboard.

Playwright

Playwright has native support for authenticated proxies right in the browser launch options:

• When calling `chromium.launch()` (or `firefox`/`webkit`), pass the object `proxy: { server: 'protocol://host:port', username: 'your-username', password: 'your-password' }`.
• The same `proxy` object can also be passed to `browser.newContext()`, if you want different proxies per context within the same process.
• Use `page.goto()` on an IP-check page as the first step of your test, confirming the connection before the rest of the flow.

Selenium

Selenium doesn't have native support for username/password proxy authentication in most drivers — the most reliable path is running through Selenium Grid with a dedicated node behind your Mobile Proxy (the whole node exits through that IP, no per-session auth needed), or using a browser extension for proxy authentication. If your workflow already uses Grid, just point the node/container to use your proxy's host and port as the default network egress.

Tips that apply to all three

• Always validate the connection at the very start of the flow with a simple IP check — it saves you from debugging a test that's actually just a wrong port or credential.
• Don't reuse your proxy credentials across parallel runs that need different IPs — that defeats the purpose of exclusivity.
• Note your plan's expiration date; the proxy is automatically shut down on that date, and renewing on time avoids connection failures in automated pipelines.

If nothing connects

Check, in this order: whether the host/port were copied without extra spaces, whether the protocol configured in the tool matches your proxy's, and whether the plan is still valid in your dashboard. If everything checks out and the connection still fails, open a ticket via email or Telegram — our team confirms the infrastructure is up on our end.

Related articles

• Why a new number alone doesn't fix WhatsApp automation blocks
• Is a free proxy worth it? The risks nobody mentions