Proxies and launch refusals

Error codes: signed_chrome.proxy_required, proxy.blocklist_too_large, proxy.pool_exhausted, profile.launch_refused

Browz supports HTTP, HTTPS, SOCKS4 and SOCKS5 proxies. SOCKS4 takes a user ID only. SOCKS5 works with or without authentication: give both a username and a password, or neither. An HTTPS proxy has its TLS certificate verified before credentials are sent.

1. Open Proxies and choose + Add, or Bulk import to paste several at once.
2. Choose Check on the proxy row. Browz connects through the proxy and reports the real exit IP and location.
3. Assign the proxy to a profile in the new-profile panel or in the profile drawer.

A profile with a proxy is always checked at Start: if its proxy does not carry an exit lookup, Start is refused, and Browz never launches it on this computer's own connection instead.

Settings, Network and proxies holds three further launch checks. All three are off by default: Only launch with a working proxy (which refuses a profile that has no proxy), Refuse if the exit country changed, and Refuse when the exit timezone is disputed. When a check fails, Start is refused with a message that begins REFUSING TO LAUNCH and names the profile.

Installed Chrome profiles always require a proxy, whatever the Only launch with a working proxy setting says.

Destination DNS on each proxy is Remote (proxy resolver) by default. Local (machine resolver) exposes the domains you visit to this computer's DNS. WebRTC is set in Settings, Network and proxies; derive from the proxy is recommended, and real leaks the host IP.

Fix a proxy that is not working →

Exit country changed or disputed →

Still stuck? Export diagnostics and contact support.