How to Fix “ERR_PROXY_CONNECTION_FAILED” in Google Chrome

The error message “ERR_PROXY_CONNECTION_FAILED” (accompanied by the notice “There is no Internet connection – There is something wrong with the proxy server, or the address is incorrect”) occurs in Google Chrome when the web browser is instructed to route outbound HTTP/HTTPS requests through an intermediary proxy server that is offline, misconfigured, or unreachable. Because Chrome inherits system-level network proxy parameters by default, a corrupted proxy configuration or lingering VPN driver will sever web access across all websites. Resolving this issue involves auditing local proxy toggles, resetting WinHTTP configuration tables, and disabling conflicting browser extensions.

Understanding Why Chrome Throws ERR_PROXY_CONNECTION_FAILED

When a web browser connects to a remote server, it queries the local operating system’s network configuration to determine whether network packets should be dispatched directly via the local gateway or routed through a proxy server (such as an HTTP, HTTPS, or SOCKS proxy). If proxy interception is enabled—either manually, via an automated configuration script (PAC file), or through malware—Chrome attempts to complete a Transmission Control Protocol (TCP) handshake with that intermediary host. If the proxy fails to respond or refuses the connection, Chrome terminates the request and displays ERR_PROXY_CONNECTION_FAILED.

Common triggers include:

• Unintended Local Proxy Settings: Windows or macOS proxy settings inadvertently activated by third-party VPNs, public Wi-Fi portals, or outdated corporate configurations. If your operating system struggles with proxy detection, see our guide on fixing Windows could not detect network proxy settings.
• Stale VPN Virtual Adapters: Virtual private network clients that terminate abnormally without cleanly deregistering their local proxy endpoints.
• Rogue Browser Extensions: Ad-blocking, privacy, or proxy extensions that reroute traffic through defunct nodes.
• Corrupted WinHTTP Proxy Tables: Low-level Windows HTTP services retaining stale proxy directives independently of graphical user interface toggles.

Layer	Role in Routing	Failure Condition
Chrome Proxy Handler	Evaluates extension and system proxy policies	Extension forces traffic to unavailable host
Windows Proxy Settings	Supplies global proxy IP and port to WinINet	Manual proxy toggle enabled with invalid port
WinHTTP Proxy Table	Controls system and service-level HTTP traffic	Stale proxy IP cached in system registry
Network Adapter Stack	Manages physical IP addressing and DNS resolution	DNS cache poisoning or dynamic network change (see fixing ERR_NETWORK_CHANGED in Chrome)

Step 1: Disable Proxy Settings in Windows 11

Most home and personal workstation connections do not require a proxy server. Verifying that automatic and manual proxy options are disabled restores direct internet routing.

1. Press Windows Key + I to open the Settings app.
2. Navigate to Network & internet in the left pane, then click Proxy.
3. Under the Automatic proxy setup section:
   • Ensure Automatically detect settings is toggled Off (or On if your institutional network specifically requires WPAD).
   • Ensure Use setup script is set to Off.
4. Under the Manual proxy setup section:
   • Next to Use a proxy server, click Edit.
   • Toggle the switch to Off and click Save.
5. Restart Google Chrome and test whether websites load normally.

Step 2: Clear Proxy Configurations via Internet Properties

Legacy WinINet configurations stored in the classic Control Panel can occasionally override modern Windows 11 Settings toggles.

1. Press Windows Key + R, type inetcpl.cpl, and press Enter to open Internet Properties.
2. Select the Connections tab at the top.
3. Click the LAN settings button near the bottom.
4. Untick the checkbox labelled Use a proxy server for your LAN.
5. Tick Automatically detect settings to allow standard DHCP resolution.
6. Click OK, then click Apply and OK in the parent window.

Step 3: Reset WinHTTP Proxy Configuration via Elevated Terminal

Windows services and Chromium-based browsers sometimes retain proxy parameters in the WinHTTP subsystem that remain invisible within standard settings menus. Resetting this layer forces direct routing.

1. Press Windows Key + X and choose Terminal (Admin).
2. Check the current WinHTTP proxy configuration by executing:

netsh winhttp show proxy

3. If the output lists a proxy server rather than “Direct access (no proxy server)”, reset the configuration by running:

netsh winhttp reset proxy

4. Flush local network caches to ensure clean DNS and socket resolution:

ipconfig /flushdns
netsh winsock reset

Restart your computer to finalise the socket reset.

Step 4: Audit and Disable Conflicting Chrome Extensions

Third-party extensions can programmatically control Chrome’s internal proxy settings using the chrome.proxy API, triggering errors even when Windows settings appear clean.

1. Open Google Chrome, type chrome://extensions in the address bar, and press Enter.
2. Locate any VPN, ad-blocker, or security extensions.
3. Toggle them Off one by one, or click Remove.
4. Alternatively, navigate to chrome://settings/system.
5. If an extension is managing your connection, you will see a notice stating: “Google Chrome is using an extension to control your proxy settings.” Click Disable directly beside the alert.

Step 5: Reset Chrome Flags and Network Predictions

Experimental flags or corrupted prefetching protocols can interfere with network socket handshakes.

1. Type chrome://flags into Chrome’s address bar and press Enter.
2. Click the Reset all button at the top of the page.
3. Next, go to chrome://settings/reset and select Restore settings to their original defaults.
4. Click Reset settings. This restores homepage, search engine, and tab preferences while disabling rogue extensions without touching your saved passwords and bookmarks.