sodcalculator

10 Tech How-To

ERR_EMPTY_RESPONSE Fix in Chrome & Edge

Guide 10-51751 · Updated · Step by step

If you see ERR_EMPTY_RESPONSE in Chrome or Edge, the server closed the connection without sending any data. The fix usually involves clearing your DNS cache, disabling proxy/VPN extensions, or flushing the socket pool—start with the steps below.

What Causes ERR_EMPTY_RESPONSE?

This error appears when the browser sends a request to a website, but the server returns nothing—not even an error code. It’s different from ERR_CONNECTION_RESET (which means the connection was actively terminated) or ERR_INTERNET_DISCONNECTED (no network at all). Common triggers include:

  • Corrupted DNS cache on your device
  • A misbehaving proxy or VPN extension
  • Outdated network drivers or a faulty router
  • Firewall or antivirus blocking the connection
  • Server-side issues (the site itself is down)

Because the causes vary, you’ll need to try several fixes in order—most users resolve it with the first two or three.

Quick Fixes to Try First

  1. Reload the page (Ctrl+F5) to force a fresh request.
  2. Restart your router and modem—power them off for 30 seconds, then back on.
  3. Try another browser or your phone’s mobile data. If the site loads elsewhere, the problem is local to your computer or network.
  4. Disable your VPN or proxy temporarily. Many VPNs and “secure DNS” services can cause this error.

If the error persists, move on to the system-level fixes below.

Clear DNS Cache and Flush Socket Pools

Your computer stores DNS lookups and network sockets. When they become stale or corrupted, you get ERR_EMPTY_RESPONSE. Here’s how to clear them:

  1. Press Windows + R, type cmd, and press Ctrl+Shift+Enter to open Command Prompt as administrator.
  2. Run these commands one by one, pressing Enter after each:
    ipconfig /flushdns
    netsh winsock reset
    netsh int ip reset
  3. Restart your computer.

For macOS, open Terminal and run sudo dscacheutil -flushcache (then enter your password). This clears the DNS cache but doesn’t reset sockets—a reboot handles that.

Disable Proxy and VPN Extensions

Browser extensions that route traffic—like ad blockers, VPNs, or “smart proxy” tools—can interfere with the connection. To test:

  1. Open Chrome or Edge, click the three-dot menu, then Extensions (or More tools → Extensions).
  2. Toggle off all extensions, then reload the page.
  3. If the page loads, turn extensions back on one at a time to find the culprit.

Also check your system proxy settings: in Windows, go to Settings → Network & Internet → Proxy and ensure “Use a proxy server” is off (unless you know you need it). On macOS, check System Settings → Network → Details → Proxies.

Check Firewall and Antivirus Settings

Security software sometimes blocks connections it considers suspicious—especially if the site uses a non-standard port or a self-signed certificate. To test:

  1. Temporarily disable your antivirus real-time protection (not the firewall yet).
  2. Reload the page. If it works, add the site to your antivirus whitelist.
  3. If not, disable the Windows firewall temporarily (Start → type “Windows Defender Firewall” → Turn off) and test again. Re-enable it immediately after testing.

If disabling both fixes the issue, you’ll need to configure an exception for the specific site or port—don’t leave your firewall off.

Reset Browser Settings and Network Stack

If nothing above works, reset the browser to its default state. This clears cache, cookies, and site data, and disables all extensions—but it also removes saved passwords and bookmarks (though you can export them first).

  1. In Chrome: Settings → Reset and clean up → Restore settings to their original defaults.
  2. In Edge: Settings → Reset settings → Restore settings to their default values.

After resetting, test the problematic site. If it still fails, the issue is likely network-wide. Try changing your DNS server to a public one like Google (8.8.8.8) or Cloudflare (1.1.1.1) in your router or OS settings—this often bypasses ISP-level DNS problems.

When the Problem Is the Server

Sometimes ERR_EMPTY_RESPONSE isn’t your fault. The website’s server may be overloaded, down, or blocking your IP. To check:

  • Use a site like downforeveryoneorjustme.com (or similar) to see if the site is down for everyone.
  • Try accessing the site via a different network (e.g., smartphone hotspot). If it loads there, your ISP or router is the issue.
  • If the site is down, wait and retry later—no local fix will help.

For site owners, this error can also appear if your web server (Apache, Nginx) is crashing or if the PHP/Node process is timing out. Check server logs for “empty reply” entries.

Frequently Asked Questions

Why does ERR_EMPTY_RESPONSE happen only on one website?

If only one site fails, it’s likely a server-side issue or that site’s specific configuration (e.g., it blocks your IP or uses an outdated SSL certificate). Try a different device on the same network—if it works there, the problem is your browser or OS.

Can a VPN cause ERR_EMPTY_RESPONSE?

Yes. VPNs route your traffic through a remote server, and if that server is misconfigured or blocked by the target site, you’ll get an empty response. Disconnect the VPN and test. If the site loads, switch to a different VPN server or disable the VPN for that site.

Does clearing browser cache help with this error?

Sometimes. A corrupted cache entry can cause the browser to send a malformed request. Clearing cache and cookies (especially for the affected site) is a quick, harmless step. To clear just one site: open DevTools (F12) → Network tab → check “Disable cache” → reload.

Is ERR_EMPTY_RESPONSE a sign of malware?

Not typically. Malware can cause network issues, but this error is more often due to DNS, proxy, or server problems. If you also see other symptoms (redirects, pop-ups), run a malware scan with Windows Defender or a trusted tool.

Will resetting my router fix this error?

Often yes. A router with a corrupted NAT table or DNS cache can cause empty responses. Restart it by unplugging for 30 seconds. If that doesn’t help, try resetting it to factory defaults (but you’ll need to reconfigure your Wi-Fi settings).

What if none of these fixes work?

If you’ve tried all steps and the error persists on multiple sites, the problem may be with your ISP or a deeper OS issue. Try booting into Safe Mode with Networking (Windows) or a different user account on macOS. If it works there, a background app is interfering. Otherwise, contact your ISP.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →