Bright Data proxies need selenium-wire, not plain selenium - pass proxy auth via seleniumwire_options

TL;DR

Pass the proxy dict via seleniumwire_options at driver creation: http and https keys both set to your Bright Data proxy server address with your Bright Data username and password as the proxy credentials. The asker's fix was exactly this: changing the import from selenium.webdriver to selenium-wire's webdriver and passing the proxy options in. Bright Data proxies do not work with a plain selenium driver - the proxy auth needs selenium-wire.

Fix

1. Pass the proxy dict via seleniumwire_options at driver creation: http and https keys both set to your Bright Data proxy server address with your Bright Data username and password as the proxy credentials. Expected: You get the expected result; the problem is gone.

2. The asker's fix was exactly this: changing the import from selenium.webdriver to selenium-wire's webdriver and passing the proxy options in. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Bright Data proxies need selenium-wire, not plain selenium - pass proxy auth via seleniumwire_options.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source.

Variant phrasings

Bright Data proxies need selenium-wire, not plain selenium - pass proxy auth via seleniumwire_options

Why it happens

Stack Overflow (Selenium Proxy with Bright Data chrome driver, accepted answer): the working pattern wires Bright Data's proxy through selenium-wire by passing proxy config in seleniumwire_options at driver creation: a proxy dict with http and https keys pointing at your Bright Data proxy server, with your Bright Data username and password supplied as the proxy credentials. Plain selenium.webdriver does not accept this; you need selenium-wire's driver so the proxy auth is handled for HTTPS targets.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Stack Overflow (Selenium Proxy with Bright Data chrome driver, accepted answer): the working pattern wires Bright Data's proxy through selenium-wire by passing proxy config in seleniumwireoptions at driver creation: a proxy dict with http and https keys pointing at your Bright Data proxy server, with your Bright Data username and password supplied as the proxy credentials. Plain selenium.webdriver does not accept this; you need selenium-wire's driver so the proxy auth is handled for HTTPS targets. Resolved: Bright Data proxies do not work with a plain selenium driver - the proxy auth needs selenium-wire. Pass the proxy dict via seleniumwireoptions at driver creation: http and https keys both set to your Bright Data proxy server address with your Bright Data username and password as the proxy credentials. The asker's fix was exactly this: changing the import from selenium.webdriver to selenium-wire's webdriver and passing the proxy options in. If your Selenium traffic is leaking around the proxy, this is the missing piece. Source: https://stackoverflow.com/questions/75256075