ERR_EMPTY_RESPONSE Error? Don’t Panic — Do This First

You open Chrome, enter a URL, and wait. The browser keeps spinning for a few while —and then, browser displays a blank page with one message: ERR_EMPTY_RESPONSE. No half-loaded page, no warning. Just nothing at all.

Unlike other errors that point to issues related to DNS or SSL, ERR_EMPTY_RESPONSE simply means this: your browser requested data from the server—but received nothing in return.

The good news is that, in most cases, this can be fixed in less than 5 minutes. This guide covers all 9 working solutions for 2026—for both general users and WordPress site owners—starting with the fastest solutions.

ERR_CONNECTION_RESET: How to Fix It Fast

Instant Fixes — Try These First

Before diving deeper, try these quick checks. For most users, these fix the error in just a few seconds:

Hard refresh the page — Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to bypass cache.

Try Incognito mode — press Ctrl + Shift + N. If it opens, the issue is caused by the cache or extensions.

Check other websites — If other sites are loading correctly, the problem is related to that specific server.

Restart your router — unplug it for 30 seconds, plug it back in, and wait for 60 seconds.

Temporarily disable your VPN or antivirus — these tools often block server responses without any warning.

Switch to mobile data — If the site loads on data, the issue lies with your Wi-Fi or ISP.

What is ERR_EMPTY_RESPONSE?

Definition: ERR_EMPTY_RESPONSE occurs when your browser successfully connects to a website's server and sends an HTTP request—but the server closes the connection without sending back any data. The browser receives a completely empty response and display this error instead of the page.

This is distinct from a ‘timeout’ (when the server takes too long) or a ‘connection reset’ (when the connection breaks midway through the handshake). In the case of ERR_EMPTY_RESPONSE, the connection does open—but the server immediately goes silent.

Chrome displays this as ERR_EMPTY_RESPONSE, Firefox displays it as “The connection was reset.” Edge displays it as “Hmmm… can’t reach this page.” The problem is the same; only the wording differs.

Why Does This Error Occur?

ERR_EMPTY_RESPONSE is one of the most common browser errors—it can be caused by your browser, your network, or the server itself. All known causes are listed here:

• Corrupted Browser Cache — Outdated or broken cache data causes the browser to send a malformed request that the server is unable to respond to.
• Browser Extensions — Privacy, VPN, or ad-blocker extensions intercept requests and offer nothing in return.
• Corrupted Windows Temp Files — Excessively large or broken Temp files disrupt browser communication at the OS level.
• Corrupted DNS Cache — Outdated DNS entries redirect the browser to an incorrect or defunct server address.
• Misconfigured TCP/IP or network stack — Corrupted network settings prevent proper data exchange.
• Antivirus or firewall blocking response — Security tools intercept the server’s response and remove it.
• Server-side crash or overload — The website’s server is down, exhausted, or misconfigured to send empty responses.
• WordPress .htaccess corruption — A broken .htaccess file causes Apache to close connections without sending data.
• Conflicting WordPress plugins — A faulty plugin crashes PHP execution before any output is sent to the browser.

Step-by-Step Solution to Fix ERR_EMPTY_RESPONSE

1. Clear Browser Cache and Cookies

Corrupted cached data is the most common cause of this error, and clearing it takes less than 60 seconds.

• Press Ctrl + Shift + Delete in Chrome (or Cmd + Shift + Delete on Mac).
• Set Time Range to “All time.”
• Check Cookies and other site data and Cached images and files.
• Click Clear data. Relaunch Chrome and test the site again.

⚠️ Deleting cookies will log you out of all sites. Save any important passwords before proceeding.

2. Clear Chrome’s Internal DNS Cache

Chrome maintains its DNS cache separately from Windows—and most guides skip this step entirely. Even after flushing the system DNS, Chrome may continue to use old records.

• In Chrome’s address bar, type: chrome://net-internals/#dns
• Click Clear host cache.
• Then go to chrome://net-internals/#sockets
• Click on ‘Flush socket pools‘ — this clears out old open connections.
• Reload the page and check if the error is gone.

3. Clean Windows Temp Files 

Corrupted Windows temporary files interfere with browser operations at the OS level. This solution is rarely mentioned—yet, surprisingly, it often works.

• Press Win + R, type %temp%, and press Enter.
• Press Ctrl + A to select all files in the Temp folder.
• Press Delete — skip any files that show “in use” errors.
• Relaunch Chrome and test the site again.

4. Disable Browser Extensions

A problematic extension—particularly a VPN, privacy, or ad-blocker add-on—can intercept the server’s response and return nothing, resulting in this exact error.

• Go to chrome://extensions in your address bar.
• Toggle all extensions off at once.
• Try loading the site. If it works — re-enable extensions one by one.

5. Flush DNS Cache and Reset Network 

Outdated DNS entries and a corrupted network stack are common causes—especially after Windows updates or changing a router.

• Open Command Prompt as Administrator.
• Run these commands one by one:
• ipconfig /release → ipconfig /flushdns → ipconfig /renew
• netsh int ip set DNS → netsh winsock reset
• Restart your computer and test the site again.

6. Disable Antivirus or Firewall Temporarily

Security software sometimes removes server responses that it deems suspicious—leaving the browser with a completely empty result. Verify this carefully.

• Right-click your antivirus icon in the system tray → Disable temporarily (10–15 minutes).
• For Windows Firewall: Control Panel → Windows Defender Firewall → Turn off (temporarily).
• Test the site. If it loads — whitelist it in your security software settings.
• Re-enable security software immediately after testing.

7. Change DNS Server

It is possible that your ISP’s DNS is directing your browser to a server address that is down or inaccessible. Switching to Google or Cloudflare DNS initiates a new lookup from a trusted source.

• Go to Control Panel → Network & Sharing Center → Change adapter settings.
• Right-click your active connection → Properties → IPv4 → Properties.
• Select “Use the following DNS server addresses.”
• Enter: Preferred: 8.8.8.8 / Alternate: 8.8.4.4 — or use Cloudflare: 1.1.1.1 / 1.0.0.1
• Click OK then flush DNS (Method 5) to apply changes immediately.

8. Reset Google Chrome Settings

If this error persists across all websites and all other troubleshooting methods have failed, it is possible that Chrome’s internal settings have become severely corrupted. A complete reset restores it to its factory settings.

• In Chrome, go to chrome://settings/reset
• Click “Restore settings to their original defaults.”
• Click Reset settings in the confirmation dialog.
• Restart Chrome and test the site again.

⚠️ This will reset your startup page, new tab page, search engine, and pinned tabs. Bookmarks and passwords will not be deleted.

9. For WordPress Site Owners — Fix .htaccess and Plugins

If visitors are seeing this error on your WordPress site, a corrupted .htaccess file or a broken plugin is almost always the cause.

• Fix .htaccess: Log in to cPanel → File Manager → enable hidden files → find .htaccess in your root folder.
• Rename it to .htaccess_old to disable it temporarily. Test your site.
• If the site loads — go to WordPress Dashboard → Settings → Permalinks → click Save Changes to regenerate a clean .htaccess.
• Fix plugins: Via FTP or cPanel, rename the /wp-content/plugins/ folder to /plugins_old/
• Test your site. If it loads — rename it back and deactivate plugins one by one to find the culprit.

How to Prevent ERR_EMPTY_RESPONSE

• Clear your browser cache and temp files regularly — at least once a month.
• Keep Chrome, Windows, and all extensions updated to their latest versions.
• Use reliable public DNS like Google 8.8.8.8 or Cloudflare 1.1.1.1 as your default.
• If you run a WordPress site, back up your .htaccess file before installing new plugins or themes.
• Audit and remove unused Chrome extensions every few months — fewer extensions means fewer conflicts.

Best Practices

The Chrome socket flush (Method 2) — going to chrome://net-internals/#sockets and clicking Flush socket pools — is one of the most effective fixes for ERR_EMPTY_RESPONSE. Almost no mainstream guide mentions it, yet it clears stale open connections that keep triggering empty responses.

Cleaning the Windows Temp folder (Method 3) is underrated. Temp files slow down Chrome's communication with servers. Make this part of your monthly PC maintenance routine — it prevents multiple browser errors, not just this one.

If you're a WordPress site owner and the error just started after installing a plugin or updating a theme — that's almost always the cause. Rename the plugins folder via FTP as a first step — it's faster than deactivating plugins one by one from the dashboard.

Frequently Asked Questions