/diagnostic/ — Browserbase: tunnel connection failed
Check location selection and proxy connectivity when a Browserbase session reports ERR_TUNNEL_CONNECTION_FAILED.
Troubleshooting. Official documentation · Checked · Review due .
documented capabilities
CDP / WebSocket- Possible causes
- The documentation lists an unsupported site, unsupported city or temporary proxy issue.[1]
- Location check
- Retry without city targeting or choose another city.[1]
- Custom proxy check
- Custom proxy connectivity is validated when the session is created; unreachable endpoints or incorrect credentials can fail creation.[1]
Billing: Browserbase plan and proxy usage charges apply; this reference does not estimate retry costs.
Outputs: Diagnostic guidance
Documented for: Playwright, Puppeteer
checks to make
documentation reviewed- Check the requested location and proxy configuration.
- For a temporary issue, retry the session; consult the source for site restrictions.
Requirements & limitations
- The error alone cannot establish which cause applies.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
1 references- Browserbase proxy troubleshooting and custom proxiesChecked 2026-09-27