Selenium proxy setup
Configure a NobleProxy dedicated static residential proxy in Selenium with the exact fields the app asks for, then run its connection check before real tasks.
Quick answer
Add your NobleProxy host, port, username, and password to Selenium's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.
Configure a NobleProxy dedicated static residential proxy in Selenium with the exact fields the app asks for, then run its connection check before real tasks.
Add your NobleProxy host, port, username, and password to Selenium's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.
| Proxy type / protocol | HTTP or SOCKS5 - both supported on every NobleProxy endpoint |
|---|---|
| Host / endpoint | The host exactly as issued in your NobleProxy dashboard |
| Port | The port paired with your endpoint in the dashboard |
| Username | Your NobleProxy credential (case sensitive) |
| Password | Your NobleProxy credential (case sensitive) |
| Static or rotating | Static - the same exit IP every session by design |
Field labels vary slightly between app versions; the NobleProxy values never change.
Create a Proxy with httpProxy and sslProxy set to host:port from your NobleProxy dashboard and add it to the browser options.
Register the username and password the way your driver supports, or confirm the endpoint was provisioned for IP-based auth if your plan allows it.
Open an IP echo page as the first navigation and confirm it reports the endpoint address.
Stop and relaunch the driver to change endpoints; Selenium does not hot-swap proxies mid-session.
The tool reports the endpoint IP or country, and target pages load without credential prompts.
A refused connection, timeout, or repeated credential prompt means the host, port, username, or password does not match the dashboard values exactly.
Facts last reviewed 2026-09-01.
Selenium configures proxies through browser capabilities using a Proxy object. Python bindings raise errors late when credentials are wrong, so headless runs can silently answer 407 unless authentication is handled explicitly.
Record which profile uses which endpoint before you start. When every task or profile has one stable residential endpoint, its session history stays consistent across restarts and team handoffs.
NobleProxy endpoints support HTTP and SOCKS5. Pick the protocol Selenium asks for in its proxy dialog; both use the same host, port, username, and password.
Use the host, port, username, and password exactly as issued in your NobleProxy dashboard. Enter them in the same fields Selenium shows in its proxy configuration screen.
Yes. Map one dedicated static residential proxy to one profile and keep that mapping stable. Reusing the same endpoint for many profiles links their sessions together.
Selenium headless runs commonly surface this exact status.
View pageThe stable endpoint type behind repeatable test runs.
View pageFix the matching proxy error.
View pageAdjacent guide for the same task family.
View pageBuy self-serve now, or talk with us about a larger agency inventory.