ERR_PROXY_CONNECTION_FAILED in Chrome: Complete Fix Guide

By /

ERR_PROXY_CONNECTION_FAILED in Chrome: Complete Fix Guide

The ERR_PROXY_CONNECTION_FAILED error in Google Chrome indicates that the browser attempted to route traffic through a proxy server but failed to establish a connection. This error blocks all browsing activity and can appear suddenly even if your proxy was working minutes earlier.

This guide provides a systematic approach to diagnosing and resolving this error across Windows, macOS, and Linux, covering both intentional proxy configurations and cases where proxy settings were applied without your knowledge.

Understanding the Error

When Chrome encounters ERR_PROXY_CONNECTION_FAILED, it means one of the following occurred:

  • Chrome is configured to use a proxy, but it cannot reach the proxy server
  • A system-level proxy setting is directing Chrome through an unavailable proxy
  • A browser extension is injecting proxy settings that point to a non-functional server
  • A PAC (Proxy Auto-Configuration) script is returning an invalid proxy address

Chrome does not manage its own proxy settings on Windows and macOS. Instead, it inherits proxy configuration from the operating system. This means the fix often involves changing system settings rather than Chrome settings.

Fix 1: Check Chrome’s Proxy Settings

Start by examining what proxy configuration Chrome is currently using:

  1. Open Chrome and navigate to chrome://settings/
  2. Search for “proxy” in the settings search bar
  3. Click “Open your computer’s proxy settings”

This opens the OS-level proxy configuration panel. If a proxy is configured here that you did not set up, it may have been injected by malware, a VPN client, or an enterprise policy.

Windows

  1. Navigate to Settings > Network & Internet > Proxy
  2. Under “Manual proxy setup,” check if “Use a proxy server” is enabled
  3. If you do not intend to use a proxy, toggle it off
  4. Under “Automatic proxy setup,” check if a PAC script URL is configured
  5. If unwanted, set “Automatically detect settings” to Off

macOS

  1. Open System Settings > Network
  2. Select your active connection (Wi-Fi or Ethernet)
  3. Click Details > Proxies
  4. Uncheck any proxy protocols you did not configure
  5. Click OK and Apply

Linux

Chrome on Linux respects the http_proxy, https_proxy, and no_proxy environment variables, as well as GNOME/KDE system proxy settings:

# Check current proxy environment variables
env | grep -i proxy

# Unset if needed
unset http_proxy
unset https_proxy
unset no_proxy

Fix 2: Disable Proxy Extensions

Browser extensions are a frequent source of unexpected proxy configurations. Extensions like proxy switchers, VPN extensions, and privacy tools can inject proxy settings that override system configuration.

  1. Navigate to chrome://extensions/
  2. Disable all extensions
  3. Restart Chrome and test

If the error disappears, re-enable extensions one at a time to identify the culprit. Pay particular attention to:

  • Proxy SwitchyOmega
  • FoxyProxy
  • Any VPN browser extension
  • Ad blockers with proxy-based filtering

Once you identify the problematic extension, check its configuration for incorrect proxy addresses or ports.

Fix 3: Reset Chrome Flags and Network Settings

Experimental Chrome flags can occasionally interfere with proxy connections:

  1. Navigate to chrome://flags/
  2. Click “Reset all to default”
  3. Restart Chrome

Additionally, clear Chrome’s DNS and socket pools:

  1. Navigate to chrome://net-internals/#dns
  2. Click “Clear host cache”
  3. Navigate to chrome://net-internals/#sockets
  4. Click “Close idle sockets” then “Flush socket pools”

Fix 4: Flush DNS Cache

Stale DNS entries can prevent Chrome from resolving the proxy hostname:

Windows

ipconfig /flushdns

macOS

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux

sudo systemd-resolve --flush-caches

After flushing DNS, restart Chrome and attempt the connection again.

Fix 5: Check for Malware

Malware frequently modifies proxy settings to intercept web traffic. If you did not configure a proxy and one appeared in your settings, run a full malware scan.

Chrome includes a built-in cleanup tool on Windows:

  1. Navigate to chrome://settings/cleanup
  2. Click “Find” to scan for harmful software

On macOS and Linux, use your preferred antivirus solution. Also check for suspicious PAC file URLs in your proxy auto-configuration settings, as these can redirect all traffic through a malicious server.

Fix 6: Verify the Proxy Server Is Running

If you intentionally configured a proxy, verify that the proxy server is operational:

# Test TCP connectivity to the proxy
nc -zv proxy-host 8080

# Test with cURL
curl -x http://user:pass@proxy-host:8080 https://httpbin.org/ip

If using mobile proxies, log in to your provider dashboard and confirm your proxy endpoint is active and your subscription has not expired.

Fix 7: Update the Proxy Configuration

If your proxy provider has changed their infrastructure, your saved proxy settings may point to a decommissioned server. Check your provider’s documentation for:

  • Updated gateway addresses
  • New port numbers
  • Changed authentication requirements
  • Updated PAC file URLs

Update your system proxy settings with the current values.

Fix 8: Reset Network Configuration

As a more thorough measure, reset your entire network configuration:

Windows

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

Restart your computer after running these commands.

macOS

  1. Open System Settings > Network
  2. Select your connection and click the minus button to remove it
  3. Click the plus button to re-add it
  4. Reconnect to your network

Linux

sudo systemctl restart NetworkManager

Fix 9: Use Chrome’s Built-In Diagnostics

Chrome provides network diagnostic tools that can help identify the specific failure point:

  1. Navigate to chrome://net-export/
  2. Click “Start Logging to Disk”
  3. Reproduce the error
  4. Stop logging
  5. Upload the log file to https://netlog-viewer.appspot.com/ for analysis

The net log will show the exact point where the proxy connection fails, including DNS resolution, TCP connection, and TLS handshake stages. For an introduction to key terms used in these logs, refer to the proxy glossary.

Fix 10: Try an Incognito Window

Opening an incognito window disables all extensions and uses a fresh session:

  1. Press Ctrl+Shift+N (Windows/Linux) or Cmd+Shift+N (macOS)
  2. Try loading a website

If incognito mode works, the issue is caused by an extension or cached data in your regular profile.

Enterprise and Managed Environments

If Chrome is managed by an organization (indicated by “Your browser is managed by your organization” in settings), proxy settings may be enforced by Group Policy or MDM profiles. In this case:

  1. Navigate to chrome://policy/ to see applied policies
  2. Look for ProxyMode, ProxyServer, or ProxyPacUrl policies
  3. Contact your IT department to update or remove the proxy policy

You cannot override managed proxy settings at the user level.

Preventing the Error

After resolving the issue, take these steps to prevent recurrence:

  • Document your proxy configuration so you can quickly restore correct settings if they are changed
  • Be cautious with browser extensions that modify proxy settings. Only install extensions from trusted sources
  • Monitor for unauthorized changes to your system proxy settings, which can indicate malware
  • Keep Chrome updated to benefit from the latest network stack improvements and bug fixes
  • Use the proxy testing checklist after any configuration change to verify connectivity

Conclusion

The ERR_PROXY_CONNECTION_FAILED error in Chrome is almost always caused by a misconfigured or unreachable proxy server at the system level. Because Chrome delegates proxy management to the operating system, the fix usually involves correcting OS-level proxy settings, removing rogue browser extensions, or verifying that your proxy server is online and properly configured. Work through the fixes in order, starting with the simplest system settings checks before moving to network resets and diagnostic logging.

Related Reading

Scroll to Top