Fixing net::ERR_PROXY_CONNECTION_FAILED in Chrome and Other Browsers

Understanding the net::ERR_PROXY_CONNECTION_FAILED error

The net::ERR_PROXY_CONNECTION_FAILED error occurs when your browser tries to connect to the internet through a proxy server that is either unreachable, misconfigured, or non-existent. Essentially, the browser is following a set of instructions that say "go through this gate to get to the web," but the gate is locked or doesn't exist.

This is common after using VPNs, proxy extensions, or when working in corporate environments with strict network policies. Occasionally, malware or legacy software can also change your system's proxy settings without your knowledge, leading to a sudden loss of connectivity.

Step 1: Disable Manual Proxy Settings (Windows)

Most home users do not need a manual proxy. If you recently changed your network or uninstalled a VPN, Windows might still be looking for a proxy that is no longer there.

Press Win + R, type inetcpl.cpl, and press Enter.
Go to the Connections tab and click on LAN settings.
Uncheck "Use a proxy server for your LAN".
Ensure "Automatically detect settings" is checked.
Click OK and Apply, then restart your browser.

Step 2: Check Proxy Configuration on macOS

On macOS, proxy settings are managed within the System Settings. A stray configuration here will cause net::ERR_PROXY_CONNECTION_FAILED across all browsers, including Safari and Chrome.

Click the Apple menu and select System Settings (or System Preferences).
Navigate to Network and select your active connection (Wi-Fi or Ethernet).
Click Details... and then select the Proxies tab.
Toggle off any active proxies like "Web Proxy (HTTP)" or "Secure Web Proxy (HTTPS)" unless you explicitly know you need them.
Click OK and test your connection.

Step 3: Reset Network Stack and DNS Cache

Sometimes the issue isn't just the proxy setting itself, but a corrupted network stack or DNS cache. Resetting these can clear out stale configurations that are forcing the browser into a failed state.

For Windows Users:

Open Command Prompt as Administrator and run the following commands one by one:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer after running these commands to ensure the changes take effect.

For Linux Users:

If you are seeing this on a Linux workstation, check your environment variables. Open your terminal and run:

env | grep -i proxy

If you see http_proxy or https_proxy defined and you aren't on a corporate network, you may need to unset them in your .bashrc, .zshrc, or /etc/environment. To temporarily unset them for testing:

unset http_proxy
unset https_proxy
unset ftp_proxy

Step 4: Audit Browser Extensions

Browser extensions like Proxy SwitchyOmega or various VPN add-ons can override system settings. If the error only appears in one browser, an extension is likely the culprit.

Open Chrome and type chrome://extensions/ in the address bar.
Disable any proxy or VPN-related extensions.
Try opening a website in Incognito Mode (Ctrl+Shift+N). If it works there, an extension is definitely causing the problem.

Advanced Fix: Windows Registry Check

In some cases, the proxy settings are "stuck" in the Windows Registry due to group policies or persistent malware. You can manually verify these values.

Press Win + R, type regedit, and hit Enter.
Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Look for ProxyEnable. If it is set to 1, double-click it and change the value to 0.
Delete the ProxyServer key if it exists and you don't use a proxy.

Warning: Be careful when editing the registry. Always export a backup before making changes.

Verification: How to confirm the fix

Once you have applied the changes, you should verify the connection without relying solely on the browser cache.

Use cURL: Open a terminal or PowerShell and type curl -I https://www.google.com. If you get a 200 OK response, your system-level connectivity is restored.
Hard Refresh: In your browser, press Ctrl + F5 to bypass the cache and reload the page from scratch.

Prevention and Networking Tips

To avoid net::ERR_PROXY_CONNECTION_FAILED in the future, always ensure that VPN software is closed gracefully. Improperly shutting down a VPN often leaves the system proxy settings in a "redirect" state, pointing to a local port that is no longer listening.

If you are a developer managing internal proxies or setting up complex bypass lists (No Proxy lists), precision is key. Mistyping a subnet or a CIDR range can lead to unexpected routing failures. I personally use the Subnet Calculator on ToolCraft when I need to verify network ranges for proxy exclusion lists. It’s a clean, browser-based tool that works locally, so your network data stays private while you calculate masks and broadcast addresses.

If you are working in a corporate environment, these settings might be managed by your IT department via Group Policy. If the settings revert to "Manual Proxy" after every reboot, you will need to contact your network administrator to update the PAC (Proxy Auto-Config) file or the WPAD settings.