How to Fix ERR_EMPTY_RESPONSE Error in Google Chrome

The ERR_EMPTY_RESPONSE error in Google Chrome occurs when a web browser establishes a successful TCP handshake with a remote web server, but the server abruptly drops the connection without returning any HTTP payload or status headers. Also displayed alongside the message This page isn’t working – digitash.com didn’t send any data, this issue stems from corrupted local browser cache, misconfigured proxy configurations, corrupted DNS caches, or conflicting security suites intercepting web sockets.

What Causes the ERR_EMPTY_RESPONSE Error in Chrome?

Unlike standard connection timeouts or 404 Not Found errors, an empty response indicates that communication began, but the data stream was truncated or withheld. The primary catalysts include:

  • Corrupted Chrome Host Resolver Cache: Google Chrome maintains an internal DNS and socket pool that can become desynchronised from the operating system network stack.
  • Interfering Browser Extensions: Ad blockers, privacy shields, and proxy management extensions can drop incoming data packets prematurely.
  • Misconfigured Proxy or VPN Tunnels: Virtual private network drivers or rogue proxy settings that fail to terminate upstream traffic cleanly.
  • Corrupted TCP/IP Stack or Winsock Catalog: Stale network routes preventing the proper parsing of incoming transmission packets.
  • Antivirus Web Shield Scanning: Third-party security suites terminating socket connections when inspecting deep SSL/TLS handshakes.

Step 1: Test in Incognito Mode and Disable Rogue Extensions

Third-party Chrome extensions that intercept HTTP requests frequently cause empty response errors when filtering headers.

  1. Launch Google Chrome.
  2. Click the three vertical dots in the top-right corner and select New Incognito Window (or press Ctrl + Shift + N on Windows / Cmd + Shift + N on macOS).
  3. Attempt to navigate to the problematic URL.
  4. If the website loads normally in Incognito mode, an installed extension is responsible. Navigate to chrome://extensions/.
  5. Toggle off all extensions, then re-enable them one by one while refreshing the page to identify the conflicting add-on. Remove the problematic extension permanently.

Step 2: Flush Google Chrome Host Resolver Cache and Sockets

Chrome maintains its own internal DNS resolver and socket pool independent of Windows or macOS. Clearing these caches forces Chrome to establish fresh socket connections.

  1. Open a new tab in Google Chrome.
  2. Type chrome://net-internals/#dns into the address bar and press Enter.
  3. Locate the Host resolver cache section and click the Clear host cache button.
  4. Next, navigate to chrome://net-internals/#sockets in the address bar.
  5. Click the Close idle sockets button, followed by Flush socket pools.
  6. Restart Google Chrome completely and attempt to access the destination URL again.

Step 3: Clear Chrome Browsing Data and Cached Files

Stale cookies or malformed cached assets can prevent Chrome from completing an HTTP request.

  1. Press Ctrl + Shift + Delete (or Cmd + Shift + Delete on macOS) to open the Clear browsing data panel.
  2. Set the time range dropdown to All time.
  3. Tick the checkboxes for Cookies and other site data and Cached images and files.
  4. Click Clear data.
  5. Relaunch Chrome and test the connection.

Step 4: Flush Operating System DNS and Reset TCP/IP Stack

If local network routing tables or the system DNS resolver contain stale address mappings, the connection cannot be sustained.

  1. Press Windows Key + S, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Execute the following commands sequentially, pressing Enter after each:
    ipconfig /flushdns
    ipconfig /registerdns
    ipconfig /release
    ipconfig /renew
    netsh winsock reset
    netsh int ip reset
  3. Restart your computer to allow the network stack alterations to initialise fully.

Step 5: Disable Proxy Configurations and VPN Tunnels

Stale system proxy entries force browser requests through intermediary servers that may refuse connection handshakes.

  1. Press Windows Key + I to launch Windows Settings.
  2. Navigate to Network & internet > Proxy.
  3. Ensure Automatically detect settings is toggled On.
  4. Verify that Use a proxy server under Manual proxy setup is set to Off.
  5. If you run an active VPN desktop client, disconnect the tunnel or temporarily uninstall the virtual network adapter from Device Manager to rule out driver corruption.

Step 6: Temporarily Disable Antivirus Web Shields

Certain security software suites perform deep packet inspection on HTTPS traffic. If the scanner experiences a timeout while analysing the packet stream, it discards the payload, causing Chrome to display ERR_EMPTY_RESPONSE.

  1. Open your antivirus or internet security dashboard (such as Bitdefender, Norton, or Avast).
  2. Navigate to the Web Protection or Real-Time Scanning settings.
  3. Temporarily disable HTTPS Scanning or Web Shield for 10 minutes.
  4. Refresh the affected web page in Chrome. If the page renders immediately, update your security suite or add an exception for the target domain.

Get the best tech tips delivered straight to your inbox.

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