When a proxy server blocks traffic or throws "ERR_PROXY_CONNECTION_FAILED", disable the manual proxy in Windows or macOS network settings, clear the browser's cached auto-config, and confirm no PAC file or Group Policy is forcing an outdated address. That single reset resolves most proxy-related connection failures in minutes.
Symptoms
- Browser shows "Unable to connect to the proxy server" or ERR_PROXY_CONNECTION_FAILED.
- Some sites load, others time out with no clear pattern across HTTPS and HTTP.
- Corporate apps work on VPN but public sites fail, or the reverse.
- System tray shows internet, yet every browser request hangs at "Resolving proxy...".
- Authentication popup keeps asking for proxy credentials even after entering them.
Common Causes
Stale or wrong manual proxy entry
An old IP or port remains configured after a network change, VPN test, or software install. The browser dutifully sends traffic to a host that no longer answers.
Broken PAC (auto-config) file
The wpad.dat or PAC URL returns 404, contains syntax errors, or resolves to an unreachable internal host when working from home.
Group Policy or MDM enforcement
A domain policy re-applies proxy settings every login, overriding manual changes. Common on corporate laptops taken off-network.
Malware or unwanted browser extension
Adware and hijackers modify proxy settings in the registry or in Chrome's policies to intercept traffic, redirect search, or inject ads.
Corrupted WinHTTP or Winsock state
Command-line tools, updates, or Docker networking can leave WinHTTP referencing a dead proxy while the GUI shows none configured.
Step-by-Step Fix
- Confirm whether a proxy is actually required
Ask IT or check documentation before disabling anything. On managed networks, removing the proxy will cut you off entirely. If you're on home Wi-Fi and never set one up, no proxy should be active. This decides every step that follows. - Reset proxy settings in Windows
Open Settings, go to Network & Internet, then Proxy. Toggle off "Use a proxy server" under manual setup. Leave "Automatically detect settings" on for standard home networks, off if your workplace uses a specific PAC URL. Close all browser windows before retesting. - Reset proxy settings on macOS
Open System Settings, Network, select your active interface, click Details, then Proxies. Uncheck every protocol (Web Proxy, Secure Web Proxy, Auto Proxy Discovery, Automatic Proxy Configuration). Apply and restart Safari or Chrome. Firefox uses its own proxy pane under Settings, General, Network Settings. - Flush WinHTTP and DNS state
Open an elevated Command Prompt and run: netsh winhttp reset proxy, then ipconfig /flushdns, then netsh winsock reset. Reboot afterwards. This clears background proxy references used by Windows Update, Store, and .NET apps that ignore Internet Options. - Clear browser cache and reset network settings
In Chrome or Edge, open Settings, Privacy and Security, Clear browsing data, and remove cached images and cookies for all time. Then open chrome://net-internals/#dns and flush the socket pool. Firefox users should visit about:preferences#general and set Connection Settings to "No proxy". - Scan for malware and rogue extensions
Run Windows Defender Offline scan or Malwarebytes to catch proxy-hijacking adware. In Chrome, review chrome://policy for enterprise policies you didn't install. Remove any suspicious extension with network permissions, then recheck the proxy setting, which should now stay off. - Check Group Policy and registry
On domain-joined machines, run gpresult /h report.html to see which GPO sets proxy values. Home users can inspect HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings for ProxyEnable and ProxyServer keys. Only edit these if you understand the impact; back up the branch first. - Configure a proper bypass list if you need the proxy
When the proxy is required, add internal hostnames and local subnets to the exceptions field: *.company.local;10.*;192.168.*;<local>. This routes intranet traffic direct while public traffic still passes through the proxy, avoiding the timeouts most users mistake for a broken proxy.
Common proxy error messages and the fix that usually resolves them
| Error / Symptom | Likely Cause | First Action |
|---|---|---|
| ERR_PROXY_CONNECTION_FAILED | Proxy host unreachable or wrong port | Disable manual proxy, retest |
| ERR_TUNNEL_CONNECTION_FAILED | HTTPS blocked by proxy or MITM cert missing | Install corporate root CA or bypass site |
| 407 Proxy Authentication Required | Missing or expired credentials | Re-enter domain credentials, clear saved logins |
| "Resolving proxy" hangs forever | Broken PAC / WPAD lookup | Disable Auto-detect settings |
| Works on Wi-Fi, fails on VPN | Split-tunnel bypass missing | Add internal ranges to exceptions |
| Proxy re-enables after reboot | Group Policy or malware | Check gpresult and run malware scan |
Prevention
- Document the correct proxy host, port, PAC URL, and bypass list in your onboarding notes.
- Use separate browser profiles for on-site and remote work if proxy needs differ.
- Keep endpoint protection active to block adware that rewrites proxy keys.
- Review Group Policy proxy settings before issuing devices to remote staff.
FAQ
Why does my proxy setting keep turning itself back on?
Two culprits dominate. On a work laptop, Group Policy re-applies the proxy at every login, so any manual change lasts only until the next gpupdate. On personal machines, adware writes the proxy key on startup. Run gpresult /h to identify a policy, or a full malware scan to remove the hijacker.
Should I disable "Automatically detect settings" in Windows?
On home networks, yes. WPAD lookups add a few seconds to every new connection and occasionally hijack traffic to a rogue PAC file. On corporate networks, keep it on only if IT actually publishes a wpad.dat via DHCP or DNS. When in doubt, ask before changing it.
How do I know if malware changed my proxy settings?
Signs include a proxy pointing to 127.0.0.1 on a random high port, settings that revert after you disable them, and browser redirects to unfamiliar search engines. Check chrome://policy for policies you did not configure, then run a reputable anti-malware scan and reset browser settings to defaults.
Contact our IT support team for help diagnosing persistent proxy or network configuration issues.