Proxy server errors tend to occur when Windows/browser directs to an expired proxy, or malware takes control of the settings. How to fix: Disable manual proxy configuration (via Windows Network prefs or Mac Network prefs), clear the browser cache, and remove malware that wrote the configuration.
Symptoms
- Browser shows ERR_PROXY_CONNECTION_FAILED or "Unable to connect to the proxy server"
- Pages hang, time out, or return blank while Wi-Fi still shows connected
- Only certain sites fail; the rest load normally
- Firefox works but Chrome does not, or vice versa
- Browsing dies right after a VPN disconnect or a network change
Common Causes
Stale manual proxy entry
Someone set a proxy host and port that is no longer reachable. Common after office moves, VPN cleanup, or restoring an old backup.
Group Policy or MDM enforcement
A domain policy or Intune profile keeps re-applying a proxy the user just disabled. The UI toggle appears greyed out or reverts on reboot.
Malware-installed proxy hijack
Adware and info-stealers write 127.0.0.1:8080 or a remote host into the proxy settings so they can inspect or inject traffic. Resetting alone will not stop it.
Unreachable PAC file
An Automatic Proxy Configuration URL points at a server that is down, moved, or blocked. The browser stalls for seconds before every request.
Corrupted WinHTTP or Winsock state
System-level network components hold a bad proxy value the UI does not expose. Windows updates, VPN clients, and antivirus tools are frequent culprits.
Step-by-Step Fix
- Is this a proxy for this machine?
Ask before you fix. From a home computer, the answer is nearly always no. From a corporate LAN, get the host, port, and PAC URL details from the network team. Time spent in this step is time spent chasing a tree that has fallen exactly where you expect it. - Disable manual proxy in Windows 10 or 11:
Win+I to open Settings, then Network & Internet, then Proxy. Under Manual proxy setup, disable "Use a proxy server". Keep "Automatically detect settings" on unless your admin directs you to disable it. Close the panel, open the browser again, and test again. - Reset proxy config in macOS:
System Settings > Network, select your active interface, click Details > Proxies. Clear all checkboxes for the protocols: Web, Secure Web, SOCKS, Auto Proxy Discovery, Automatic Proxy Configuration. Click Apply. If your business uses a PAC you'll need to re-enable only Automatic Proxy Configuration and paste the present URL. - Rebuild the Windows network stack from an administrator prompt:
A hung or stale WinHTTP or Winsock entry can monopolize the UI. Launch an administrator Command Prompt and type the following commands, then reboot: netsh winhttp reset proxy, netsh winsock reset, and ipconfig /flushdns. That clears the underlying proxy state, which is not always reflected in the Settings app. - Clear per-browser overrides in Chrome, Edge and Firefox
Chrome and Edge follow the system proxy, so a system reset usually covers them; still clear cache under Settings > Privacy and Security to remove stale PAC responses. Firefox is different. Open Settings > Network Settings > Settings, pick "No proxy" or "Use system proxy settings", and save. - Scan for proxy-hijacking malware and re-check afterwards
Run a full scan with Microsoft Defender Offline plus a second-opinion tool such as Malwarebytes. After cleaning, repeat step 2 or 4. Hijackers routinely write the proxy value back until the payload itself is removed, so verify the pane one more time before you call it fixed. - Add a bypass list for internal or trusted hosts
When the proxy is legitimate but a specific intranet site fails, add exceptions rather than disabling everything. In Windows Proxy settings, list hostnames or IP ranges under "Use the proxy server except for addresses that begin with the following entries", separated by semicolons. Include *.local, 10.*, and 192.168.*. - Validate the PAC file if one is configured
Paste the PAC URL into a browser; you should download a JavaScript file, not receive a 404. Open it in a text editor and confirm the FindProxyForURL logic still references live servers. A PAC pointing at a decommissioned proxy is a classic source of intermittent failures after network changes.
Common proxy error messages and the first action to take
| Error message | Explanation | Initial Action |
|---|---|---|
| ERRPROXYCONNECTION_FAILED | Browser cannot connect to the proxy host at all | Check hostname and port; turn off manual proxy if you don't need it |
| ERRTUNNELCONNECTION_FAILED | Proxy rejected the HTTPS CONNECT request | Verify if the proxy requires authentication and is allows 443 |
| 407 Proxy Authentication Required | Proxy expects credentials it did not receive | Re-enter domain\user; clear cached password in Credential Manager |
| Proxy server is refusing connections (Firefox) | Firefox has set its own proxy pointing at a dead host | Change Network Settings to "No proxy" or "Use system proxy" |
| Pages freeze for 10+ seconds after disconnect from VPN | PAC file continues to resolve to an internal server that is no longer accessible | Turn off Automatic Proxy Configuration or change PAC URL |
Prevention
- Document the required proxy, port, and PAC URL for every site or VLAN
- Push settings through GPO or MDM instead of editing individual machines
- Keep endpoint protection current so browser hijackers cannot rewrite the proxy
- Host PAC files on a highly available internal server with uptime monitoring
FAQ
Do I really need to use a proxy server at all?
Inquire with the administrator of the network. Many home office and small office networks connect direct to the internet and will only have a proxy if intentionally set up to allow filtering, caching, and so on. If no one can identify the proxy host, or that it exists, you are unlikely to need it, and you can disable manual configuration.
Why does resetting the proxy in Windows not fix Firefox?
Firefox ships with its own network stack and defaults to independent proxy settings rather than reading the OS configuration. Change it inside Firefox under Settings > Network Settings. Pick either "No proxy" or "Use system proxy settings" so that a Windows-level reset actually takes effect the next time you launch the browser.
Can malware really rewrite my proxy configuration?
Yes, and it is one of the older tricks in the book. Browser hijackers set the proxy to a local port so they can inject ads or harvest credentials, while info-stealers redirect traffic to an attacker-controlled host. Standard antivirus catches most families, but always re-inspect the proxy pane after cleanup and run netsh winhttp reset proxy for good measure.