How to Fix ‘ERR_EMPTY_RESPONSE’ in Google Chrome

Attempting to open a website in Google Chrome only to encounter a blank error canvas stating “This page isn’t working. [Domain] didn’t send any data. ERR_EMPTY_RESPONSE” indicates that the browser established a successful low-level TCP handshake with the target web server, but received zero HTTP headers, status codes, or payload bytes in return.

Because the network connection drops before application-layer data is exchanged, common triggers include corrupted Chrome socket pools, misbehaving virtual private network (VPN) tunnels, aggressive third-party antivirus web shields intercepting TLS handshakes, stale DNS records, or malfunctioning browser extensions.

Suspected Origin Technical Breakdown Primary Remediation
Stalled Chrome Socket Pool Internal TCP socket pool becomes desynchronised Flush socket pools via chrome://net-internals
Antivirus TLS Interception Security shield terminates connection when examining packets Disable HTTPS / SSL inspection in antivirus settings
Corrupted Local DNS Cache OS resolver directs traffic to dead load-balancer IPs Flush DNS cache and reset Winsock stack
Proxy / VPN Tunnel Deadlock Local loopback proxy fails to forward upstream server traffic Disable manual proxy in Windows / macOS network settings

Method 1: Flush Chrome Socket Pools via Net-Internals

Google Chrome maintains an internal persistent socket pool for HTTP/1.1 and HTTP/2 connections. Flushing these internal connection pools forces Chrome to negotiate fresh TCP streams.

  1. In the Chrome address bar, type chrome://net-internals/#sockets and press Enter.
  2. Click the Close idle sockets button.
  3. Click the Flush socket pools button immediately adjacent.
  4. Next, navigate to chrome://net-internals/#dns.
  5. Click Clear host cache to dump Chrome’s internal DNS resolution entries.
  6. Restart the browser completely and reload the problematic website.

Method 2: Test in Incognito Mode and Audit Browser Extensions

Third-party extensions—particularly privacy shields, script blockers, and proxy helpers—can terminate server responses before the DOM parser renders them.

  1. Press Ctrl + Shift + N (or Cmd + Shift + N on macOS) to open an Incognito window.
  2. Navigate to the URL that triggered ERR_EMPTY_RESPONSE.
  3. If the website loads normally, an installed extension is causing the error.
  4. Type chrome://extensions in the address bar and press Enter.
  5. Toggle off all extensions, then re-enable them one by one while testing the page to identify the culprit.

Method 3: Clear Chrome Browsing Data and Cache Partition

Accumulated temporary web assets and corrupted cookie session identifiers can cause servers to reject ongoing request pipelines without an error payload.

  1. Press Ctrl + Shift + Delete (or Cmd + Shift + Delete on Mac) to open the Delete browsing data dialog.
  2. Switch to the Advanced tab and set the time range dropdown to All time.
  3. Ensure the checkboxes for Cookies and other site data and Cached images and files are ticked.
  4. Click Delete data.
  5. Close and relaunch Google Chrome.

Method 4: Flush Operating System DNS and Reset Winsock Stack

If your operating system’s DNS resolver retains deprecated IP addresses following server migration, your computer attempts to send requests to non-responsive web endpoints.

  1. On Windows 11, search for cmd, right-click Command Prompt, and select Run as administrator.
  2. Execute the following commands sequentially, pressing Enter after each:
    ipconfig /flushdns
    ipconfig /release
    ipconfig /renew
    netsh winsock reset
  3. Restart your computer to complete the network stack reinitialization.

Method 5: Disable Manual Proxy Settings

Orphaned proxy settings left behind by uninstalled VPN software or security tools redirect web requests through dead local proxy ports.

  1. Press Windows Key + I to open Settings.
  2. Navigate to Network & internet > Proxy.
  3. Under Automatic proxy setup, ensure Automatically detect settings is turned On.
  4. Under Manual proxy setup, ensure Use a proxy server is set to Off.
  5. On macOS, check System Settings > Network > Wi-Fi > Details > Proxies and ensure all proxy protocols are unchecked.

Checking Server-Side Health

If ERR_EMPTY_RESPONSE occurs exclusively on one specific website across multiple devices and separate internet networks (e.g. mobile data vs home Wi-Fi), the server itself is crashing or dropping connections before generating an HTTP response. In this situation, the issue lies with the web host’s upstream Nginx/Apache configuration or load balancer, rather than your local workstation.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.