Fix "not a working proxy" and proxy check errors

Start checks a profile's proxy by looking up the exit through it first. If that lookup fails, Start is refused with: its proxy did not carry an exit lookup, so it is not a working proxy right now. The line after it gives the underlying error. This happens whatever the Only launch with a working proxy setting says.

1. Open Proxies and choose Check on the profile's proxy. The result shows whether the proxy is reachable and which exit it uses.
2. authentication rejected (HTTP 407), or socks5 authentication rejected (bad username or password): the proxy refused the username or password. Edit the proxy and re-enter both.
3. CONNECT refused (HTTP 502) or a similar CONNECT error: the proxy accepted you but could not reach the exit. The proxy or its exit is down; try again later or use another proxy.
4. connect proxy, followed by a connection error: Browz could not reach the proxy server at all. Check the host and port, and your own internet connection.
5. the exit lookup came back without an IP: the proxy answered but did not return an exit address. Check it again or replace it.
6. If the profile has no proxy and Only launch with a working proxy is on, Start says it has no proxy. Attach a proxy, or turn the setting off.
7. To get a fresh exit from the same kind of proxy, use Change IP on the profile.

Only launch with a working proxy decides only whether a profile without a proxy may start. A profile whose proxy fails its check is always refused, and never falls back to your own connection.

If Start reports that the website blocklist has too many hosts, shorten the blocklist in Settings, Websites.

Proxies and launch refusals →

Change IP for a profile or a pool proxy →

Still stuck? Export diagnostics and contact support.