ERR_PROXY_CONNECTION_FAILED
The browser can't reach its configured proxy
Seen in Chrome, Edge ("No internet")
A proxy server is configured, but the browser could not connect to it, so no site loads.
Common causes
- A proxy is set in system settings but is not running or not reachable from this network.
- Leftover proxy settings from a VPN, debugging tool or malware.
- A PAC script points at a proxy that no longer exists.
How to fix it
- Check the proxy settings (Windows: Settings > Network & internet > Proxy; macOS: Network settings > Proxies) and turn off any you do not need.
- If you need the proxy, confirm its address and port and that it is running.
- Scan for adware if proxy settings keep coming back.
Got a different message? Paste it into the error explainer.
Related errors
- ERR_BAD_SSL_CLIENT_AUTH_CERT · The server rejected your client certificate
- ERR_INTERNET_DISCONNECTED · The device has no network connection
- ERR_NETWORK_CHANGED · The network changed while the page was loading
- ERR_TUNNEL_CONNECTION_FAILED · The proxy could not open a tunnel to the site
- net::ERR_BLOCKED_BY_CLIENT · A browser extension blocked the request
- ERR_CACHE_MISS · The page needs form data to be resent
- ERR_UNSAFE_PORT · The browser blocks this port for security
- NET::ERR_CERT_DATE_INVALID · The certificate has expired or is not yet valid
- NET::ERR_CERT_AUTHORITY_INVALID · The certificate isn't issued by a trusted authority
- SEC_ERROR_UNKNOWN_ISSUER · Firefox doesn't recognise the certificate's issuer
- NET::ERR_CERT_COMMON_NAME_INVALID · The certificate doesn't cover this name
- ERR_SSL_PROTOCOL_ERROR · The secure connection failed during the handshake