Selenium proxy integration
Selenium drives a real browser, so the proxy is set at browser launch through the driver options rather than per request. Chrome takes a --proxy-server argument, and because Chrome will not read credentials from that flag, the reliable pattern is a small in-memory extension that supplies your Murphy username and password. The snippet below wires both together.
import zipfile
from selenium import webdriver
HOST, PORT = "gateway.murphyproxies.com", 8000
USER, PASS = "USERNAME", "PASSWORD"
# Chrome ignores credentials on --proxy-server, so ship them in a tiny
# background extension that answers the browser's auth prompt.
manifest = '{"version":"1.0","manifest_version":2,"name":"murphy",' \
'"permissions":["proxy","webRequest","webRequestBlocking","<all_urls>"],' \
'"background":{"scripts":["bg.js"]}}'
background = f'''
chrome.proxy.settings.set({{value:{{mode:"fixed_servers",rules:{{
singleProxy:{{scheme:"http",host:"{HOST}",port:{PORT}}}}}}},scope:"regular"}});
chrome.webRequest.onAuthRequired.addListener(
() => ({{authCredentials:{{username:"{USER}",password:"{PASS}"}}}}),
{{urls:["<all_urls>"]}}, ["blocking"]);
'''
with zipfile.ZipFile("murphy_proxy.zip", "w") as z:
z.writestr("manifest.json", manifest)
z.writestr("bg.js", background)
options = webdriver.ChromeOptions()
options.add_extension("murphy_proxy.zip")
driver = webdriver.Chrome(options=options)
driver.get("https://httpbin.org/ip")
print(driver.find_element("tag name", "body").text)
driver.quit()Setup in 5 steps
- 1Install the client with pip install selenium and a matching Chrome or Chromedriver.
- 2Set your Murphy host, port, username and password at the top of the script.
- 3Build the small proxy extension so Chrome can answer the authentication prompt automatically.
- 4Load it with options.add_extension() and launch the driver with those options.
- 5Open an IP echo page and read the body to confirm the browser exits through the proxy.
Selenium proxy questions
Everything you need to route Selenium through Murphy, from authentication to rotation.
Chrome ignores the username and password embedded in the --proxy-server flag and pops a native authentication dialog that Selenium cannot dismiss. Supplying the credentials through a small background extension answers that prompt automatically, which is why the snippet builds one.
It depends on the target. ISP proxies give a fast, stable session that suits logged-in flows and checkouts, while residential proxies give broad IP diversity that helps against strict anti-bot systems. Both are reachable through the same Murphy gateway, so only your credentials change.
Yes. Set the scheme to socks5 in the extension rules (or pass --proxy-server=socks5://gateway.murphyproxies.com:8000). Note that SOCKS5 proxy authentication is not supported by Chrome, so for authenticated SOCKS5 the extension pattern shown here is still the safest route.
Get credentials for Selenium
Pick the network that fits your target. ISP proxies for fast, stable sessions, residential proxies for broad IP diversity against strict anti-bot systems.