debugger_address option only supports local host:port connections, not remote wss:// URLs.
You have two practical paths.
Recommended: bridge through a CDP client
If you’re migrating Selenium scripts, connect through Playwright’s sync API — the page-automation model (navigate, locate, click, read) maps one-to-one, and you get the hardened stealth Chromium and residential proxies with no configuration.Query parameters
Alternative: keep Selenium with a local proxy
If you must keep the Selenium API, run a local WebSocket-to-TCP proxy so Chrome’s remote debugging endpoint appears as a localhost:port, e.g. via selenium-wire. This adds a moving part we don’t manage — for new code, prefer the CDP bridge above.
Selenium’s
debugger_address only supports local host:port connections. For remote CDP over WebSocket, use Playwright or Puppeteer instead.See also
- Playwright and Puppeteer connections
- Live preview & recording — watch the session or embed it in your app
- Proxies and stealth configuration