## TL;DR

If you attach a third-party proxy to BrowserCat, do not route everything through it.

## Fix

1. If you attach a third-party proxy to BrowserCat, do not route everything through it.
   Expected: you can confirm this matches your situation.

## When to use

- You are dealing with this situation.
- The symptom matches: BrowserCat proxy has a bypass list - use it to skip proxy bandwidth on non-target domains.

## 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. Source: https://www.browsercat.com/docs/browser-config/proxy.

## Variant phrasings

### BrowserCat proxy has a bypass list - use it to skip proxy bandwidth on non-target domains

## Why it happens

BrowserCat's own proxy docs: the proxy config accepts a bypass option - domains like api.google.com, example.org, or .net can be routed around the proxy. The docs call this out as a bandwidth saver: proxied traffic costs more, so bypass the domains that do not need the proxy (your own APIs, CDNs, font hosts) and only pay proxy bandwidth for the target site.

## 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.

## Source

https://www.browsercat.com/docs/browser-config/proxy