TL;DR: BrowserCat - Official docs (browsercat.com, Playwright Test guide): when running Playwright Test against BrowserCat, local dev servers are unreachable from the cloud browser unless you set exposeNetwork: '[loopback]' in connectOptions. ## The fix When your Playwright tests target a local dev server through BrowserCat, add exposeNetwork: use: { connectOptions: { wsEndpoint: 'YOUR_HOST.browsercat.com/connect', headers: { 'Api-Key': process.env.BROWSERCAT_API_KEY }, // Proxy YOUR_HOST requests to BrowserCat.

## Fix
1. BrowserCat - Official docs (browsercat.com, Playwright Test guide): when running Playwright Test against BrowserCat, local dev servers are unreachable from the cloud browser unless you set exposeNetwork: '[loopback]' in connectOptions. ## The fix When your Playwright tests target a local dev server through BrowserCat, add exposeNetwork: use: { connectOptions: { wsEndpoint: 'YOUR_HOST.browsercat.com/connect', headers: { 'Api-Key': process.env.BROWSERCAT_API_KEY }, // Proxy YOUR_HOST requests to BrowserCat.
   Expected: this specific failure stops.

## Details
Without exposeNetwork, page.goto('YOUR_HOST:3000') loads nothing and every assertion fails. Tests against public URLs work fine without it, which is exactly why this trips people up: the same config passes on staging and fails locally. Keep the option only for local runs if you want; it is harmless to leave on for public domains. Thread: docs:browsercat:playwright-test-exposenetwork

## When to use
You hit exactly this: BrowserCat: testing YOUR_HOST needs exposeNetwork set to [loopback] in BrowserCat.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
BrowserCat.

## Edge cases
- Not needed for public domains. exposeNetwork: '[loopback]', }, } The gotcha: the browser runs in BrowserCat's cloud, so its YOUR_HOST is not your machine.