ERR_EMPTY_RESPONSE: Fix the “Didn’t Send Any Data” Error

Chrome says the site didn’t send any data? Learn what ERR_EMPTY_RESPONSE means, what causes it and 12 fixes for visitors and site owners.

You click a link, the page tries to load, and then Chrome throws up its grey error screen: “This page isn’t working. example.com didn’t send any data. ERR_EMPTY_RESPONSE.”

This one is a little odd. The site isn’t down in the usual sense. Your browser reached the server and the server picked up, so the connection worked.

But then the server said absolutely nothing back: no page, no error message, not even a status code. It’s like asking someone a question, watching them open their mouth, and then they simply walk away.

That silence usually points to a problem inside the server, a security layer in front of it, or occasionally something on your own device. This guide explains what the error really means, what’s behind it, and how to fix it step by step, whether you’re just trying to read a page or you run the site.

Quick answer: how to fix ERR_EMPTY_RESPONSE

If you’re a visitor, try these in order:

  1. Reload the page and test a few other websites
  2. Try another device or network
  3. Clear cookies and cache for that site
  4. Disable extensions and try another browser
  5. Turn off your VPN and proxy
  6. Check your antivirus and firewall
  7. Flush DNS and reset your network settings

If you own the site, check these:

  1. Read the server logs for crashes
  2. Deactivate plugins and switch themes (WordPress and other CMS sites)
  3. Raise PHP limits and check your PHP version and extensions
  4. Reset your .htaccess file and test your server config
  5. Check your proxy, CDN and firewall, then contact your host

What does ERR_EMPTY_RESPONSE mean?

When you load a website, your browser sends an HTTP request, and the server is supposed to answer with something: a page, a redirect, or at least an error code such as 404 or 500.

ERR_EMPTY_RESPONSE appears when the server accepts the connection and then closes it without sending a single byte of reply. Chrome’s wording is “didn’t send any data,” and that’s literally what happened.

That makes it different from the errors people often confuse it with:

ErrorWhat happenedLikely area
ERR_EMPTY_RESPONSEConnection worked, but the server sent back nothingServer crash, bad config, security layer, proxy
ERR_CONNECTION_RESETThe connection was cut off mid-way. See our ERR_CONNECTION_RESET guideFirewall, antivirus, VPN, network equipment
ERR_CONNECTION_REFUSEDThe server rejected the connection right away. See our ERR_CONNECTION_REFUSED guideStopped service, closed port
ERR_CONNECTION_TIMED_OUTNobody answered in time. See our ERR_CONNECTION_TIMED_OUT guideOverload, dropped packets
500 Internal Server ErrorThe server answered, but with an error. See our 500 guideCode or config fault

The simplest way to remember it: with a 500, the server answers “something broke.” With an empty response, the server doesn’t answer at all, and that’s often because the process that should have answered crashed before it could.

How the error appears in different browsers

Chrome and other Chromium browsers (like Edge) use the code name ERR_EMPTY_RESPONSE. Other browsers word the same problem differently, and the message can vary by version, but you’ll see something like a dropped or interrupted connection.

BrowserTypical message
Chrome“This page isn’t working. example.com didn’t send any data. ERR_EMPTY_RESPONSE”
Edge“This page isn’t working right now. example.com didn’t send any data.”
FirefoxA connection error saying the connection was interrupted or reset while loading
Safari“Safari Can’t Open the Page. The server unexpectedly dropped the connection.”
curl“Empty reply from server”

That last one is useful. If you run curl -v against a page and see “Empty reply from server,” you’ve confirmed the same problem without a browser involved.

What causes ERR_EMPTY_RESPONSE?

Causes on your side

  • A VPN or proxy that’s mishandling traffic
  • Antivirus or firewall software interfering with a connection
  • A browser extension that blocks or alters the request
  • Corrupted cookies or cache for that website
  • Bad DNS data or broken network settings
  • Trying to open an HTTPS-only service over plain HTTP, or the other way around

Causes on the website’s side

  • The web server or a PHP worker crashed while handling the request
  • A PHP segmentation fault, memory exhaustion or runaway script ended the process
  • A faulty plugin, theme or extension broke the request handling
  • A bad rule in .htaccess or the server config
  • A reverse proxy, CDN or load balancer received nothing from the origin
  • A web application firewall or security tool silently killed the connection
  • Resource limits at the host stopped the process
  • A mismatch between HTTP and HTTPS ports, or between keep-alive settings across layers

First, find out where the problem is

Two quick checks will save you time:

  1. Try a handful of other websites. If they load, your internet is working and the issue is limited to this site, or to how your device talks to it.
  2. Open the page on your phone over mobile data. If it loads, the problem is on your computer or home network. If it fails there too, the server is the likely cause.

Site owners who see this error on every network can jump to Fix 8.

Fixes for visitors

Fix 1: Reload the page and test other websites

It may be a momentary glitch, like a server restarting or a process being recycled. Wait half a minute and reload with Ctrl+Shift+R (Cmd+Shift+R on Mac). If the page still fails but other sites work fine, move on.

Fix 2: Try another device or network

Open the same page on your phone, or switch to a different network, such as a phone hotspot.

  • Works elsewhere: the cause is your device, browser, router or ISP. Continue with Fix 3 to Fix 7.
  • Fails everywhere: the website’s server is the problem. You can wait and retry later, or let the site owner know.

Fix 3: Clear cookies and cache for that site

Corrupted cookies can make a server choke on a request, and a stored bad response can keep coming back.

In Chrome, click the icon at the left of the address bar, choose Cookies and site data or Site settings, and clear the data for that website. Or clear everything: Settings > Privacy and security > Delete browsing data, and tick Cookies and other site data and Cached images and files.

After clearing, reload the page. You may need to sign in again.

Fix 4: Disable extensions and try another browser

Browser extensions can change or block requests, and ad blockers, privacy tools, script blockers and security add-ons are the usual suspects.

  1. Open the page in a private or incognito window, which disables most extensions.
  2. If it loads, turn your extensions back on one at a time to find the one that causes the error.
  3. If it still fails, open the page in a different browser. If that works, the problem is limited to your main browser, and you can reset its settings or reinstall it.

Fix 5: Turn off your VPN and proxy

A VPN or proxy adds an extra link between you and the website, and a weak link can produce an empty response.

  • Disconnect the VPN and reload. If the page loads, try a different VPN server.
  • On Windows, go to Settings > Network & internet > Proxy and turn off any proxy you didn’t set up yourself.
  • On Mac, open System Settings > Network, select your connection, click Details, open Proxies, and untick anything that’s on.

If you’re on a work or school network that requires a proxy, check with your IT team first.

Fix 6: Check your antivirus and firewall

Security programs that inspect web traffic can interrupt a connection and make the reply never reach your browser.

  1. Turn off the antivirus web protection or HTTPS scanning feature for a minute and reload.
  2. Do the same with any third-party firewall.
  3. If the page loads, add an exception instead of leaving protection off.
  4. On Windows, also check Windows Security > Firewall & network protection to make sure your browser isn’t blocked.

Fix 7: Flush DNS and reset your network settings

Outdated DNS data or a damaged network stack can send your browser to a place that doesn’t answer properly.

Flush DNS. On Windows, open Command Prompt as administrator and run:

ipconfig /flushdns

On macOS, run this in Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

In Chrome, also visit chrome://net-internals/#dns and click Clear host cache.

Reset the Windows network stack. In an administrator Command Prompt run these, then restart:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew

Try a public DNS server like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). If you suspect DNS is the main problem, our DNS errors guide goes into more detail.

Finally, check the address you typed. If a service only speaks HTTPS and you open it with http://, or the reverse, some servers answer with nothing. Retype the address with the correct scheme and port.

Fixes for website owners and server admins

If the error shows up on many devices and networks, the problem is on your server or in front of it. These steps go from the most likely causes to the less common ones.

Fix 8: Read the server logs for crashes

Because an empty response often means a process died while handling a request, your logs are the fastest way to the real cause.

First, reproduce the error from the command line:

curl -v https://yourdomain.com/the-page

If you see “Empty reply from server,” the problem is server-side. Now look for crashes:

sudo systemctl status nginx
sudo systemctl status apache2
sudo systemctl status php8.2-fpm
sudo journalctl -u php8.2-fpm --since '1 hour ago'
dmesg | grep -i 'out of memory'

Replace the service names and PHP version with the ones you use. In the logs (often under /var/log/nginx/, /var/log/apache2/ or your PHP-FPM log), look for:

  • Segmentation fault or a child process exiting on a signal (SIGSEGV)
  • Out-of-memory kills from the operating system
  • Fatal PHP errors, especially memory exhausted or infinite recursion
  • Workers exiting or restarting repeatedly

On shared hosting you can’t read these directly. Open your control panel’s error log, or ask your host to check for crashes and resource kills at the time you saw the error. Our web hosting errors guide covers other problems to watch for.

Fix 9: Deactivate plugins and switch themes

On WordPress and other CMS sites, a broken plugin or theme is one of the most common reasons the server process dies mid-request. If the problem started after an update or a new install, suspect that first.

WordPress:

  1. If you can get into the dashboard, go to Plugins > Installed Plugins, deactivate everything, and test. Reactivate them one by one to find the culprit.
  2. If you can’t log in, connect via FTP or your host’s file manager, open wp-content, and rename the plugins folder to plugins-disabled. Then rename it back and test plugins one at a time.
  3. Switch to a default theme such as Twenty Twenty-Four, either from Appearance > Themes or by renaming your active theme’s folder in wp-content/themes.

Pay special attention to caching, security, backup, page builder and optimization plugins. Once you find the cause, update it, replace it or report it to its developer.

Fix 10: Raise PHP limits and check your PHP version and extensions

When PHP runs out of memory or hits a limit, it may die without a clean error page.

  • Memory: raise the limit in php.ini (for example memory_limit = 256M) or in wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
  • Execution time and input: check max_execution_time, max_input_vars and post_max_size if the problem happens on big pages, imports or form submissions.
  • PHP version: make sure you’re on a version your CMS and plugins support. A recent PHP upgrade, or a downgrade, can break old plugins.
  • Extensions and caches: a faulty PHP extension or a corrupted opcode cache can cause crashes. Restarting PHP-FPM or clearing the opcache is a quick test.

If you keep hitting memory limits, the longer-term fix may be a bigger plan. Our Server Size Calculator can help you estimate what your site needs.

Fix 11: Reset your .htaccess file and test your server config

A broken rule in .htaccess (Apache and LiteSpeed) or in an Nginx config can stop requests from being answered properly.

For .htaccess: connect via FTP or File Manager, back up the file, then rename it to .htaccess-old and reload the site. If that fixes it, regenerate a clean copy by going to Settings > Permalinks in WordPress and clicking Save Changes. Add your custom rules back one at a time to find the one that causes the problem.

For server configs: test them before reloading.

sudo nginx -t
sudo apachectl configtest

Fix any errors the test reports, then reload the web server. Look closely at recent changes to rewrite rules, proxy settings, timeouts and buffer sizes.

Fix 12: Check your proxy, CDN and firewall, then contact your host

If the web server itself looks fine, the empty response may be created by something sitting in front of it.

  • CDN or reverse proxy: try bypassing Cloudflare or your CDN for a test, or check its logs. A proxy that receives nothing from your origin may show its own error code, which our Cloudflare errors guide explains.
  • Web application firewall: ModSecurity, Cloudflare WAF, Sucuri and security plugins can kill a connection when a rule fires. Check their logs for blocked requests near the time of the error, then adjust or whitelist the rule.
  • Load balancer and keep-alive settings: make sure idle and keep-alive timeouts match across every layer. A request sent on a connection that was already closed can end up as an empty response. If the proxy does get a reply but it’s broken, you may see a 502 Bad Gateway instead.
  • Hosting resource limits: on shared and managed hosting, hitting CPU, memory or process limits can kill your PHP workers.

If you’re still stuck, contact your hosting provider. Give them the URL, the exact time of the error, the curl -v output showing “Empty reply from server,” and the steps you’ve already tried. Ask them to check server error logs, PHP-FPM logs and resource-limit events at that time. A message like that gets a much faster answer than “my site is broken.”

ERR_EMPTY_RESPONSE on localhost and in development

Developers run into this one a lot. If you see it while testing an app on your own machine, check these:

  • The app crashed on the request. Look at your terminal for an unhandled exception or a process that exited. Frameworks such as Node.js can drop the connection if a request handler throws an error that nothing catches.
  • Wrong protocol on the right port. Opening http://localhost:PORT for a server that expects HTTPS (or the reverse) can lead to an empty response.
  • Docker port mapping. Check that the port is published correctly, for example docker run -p 8080:80 image-name, and that the app inside listens on 0.0.0.0, not only 127.0.0.1.
  • Proxy in the middle. If you use a dev proxy or a tool like a tunneling service, restart it and try the direct address.
  • Infinite loops or huge responses. A handler that never finishes or crashes while building a big response can end the connection with no data.

ERR_EMPTY_RESPONSE on Android and iPhone

On a phone, the steps are shorter:

  • Switch between Wi-Fi and mobile data.
  • Turn airplane mode on and off.
  • Disable any VPN or content blocker.
  • Clear the browser’s cache and site data.
  • Restart the phone and router.

If the page fails on every network, the website itself is the cause.

How to prevent ERR_EMPTY_RESPONSE on your site

  • Monitor uptime and resources, so crashes and memory pressure show up before visitors notice.
  • Update carefully. Update plugins, themes and PHP in small steps, and test after each one, ideally on a staging site.
  • Keep logs on and readable. Make sure PHP-FPM, web server and application logs are enabled and rotated.
  • Set sensible limits. Give PHP enough memory and time for your biggest tasks, without leaving limits wide open.
  • Keep timeouts consistent across proxies, CDNs, load balancers and servers.
  • Test firewall and WAF changes from an outside network before relying on them.
  • Choose dependable hosting that provides clear logs and responsive support.

Does ERR_EMPTY_RESPONSE affect SEO?

It can if it keeps happening. Search engine crawlers that receive no data may retry, but repeated failures can slow down crawling and may cause pages to drop out of the index until they work again.

After you fix the problem, check Crawl stats and the Pages report in Google Search Console to make sure Google can reach your site normally.

Frequently asked questions

What does ERR_EMPTY_RESPONSE mean?

It means your browser connected to a website’s server, but the server closed the connection without sending any data back. Chrome describes it as the site “didn’t send any data.”

Is ERR_EMPTY_RESPONSE a problem on my end or the website’s?

It can be either. If the page loads on other devices and networks, your computer, browser or network is responsible. If it fails everywhere, the website’s server or a security layer in front of it is the cause.

What is the difference between ERR_EMPTY_RESPONSE and ERR_CONNECTION_RESET?

With an empty response, the connection works and then closes without a reply. With a reset, the connection is forcibly cut off. They have overlapping causes, but resets lean toward security software and network equipment, while empty responses more often come from crashing server processes.

What is the difference between ERR_EMPTY_RESPONSE and a 500 error?

A 500 error is an actual reply from the server saying something went wrong. An empty response means no reply arrived at all, often because the process crashed before it could send one.

Can a WordPress plugin cause ERR_EMPTY_RESPONSE?

Yes. A faulty or incompatible plugin can crash PHP while the page is being built. Deactivating all plugins and re-enabling them one at a time is the most reliable way to find the culprit.

Can a VPN or antivirus cause ERR_EMPTY_RESPONSE?

Yes. Both can interfere with web traffic. Disconnect the VPN and temporarily turn off web protection or HTTPS scanning to test, then add exceptions if needed.

How do I check whether the server is sending an empty response?

Run curl -v https://yourdomain.com in a terminal. If you see “Empty reply from server,” the server is closing the connection without sending data.

Why do I get ERR_EMPTY_RESPONSE on localhost?

Usually the app crashed while handling the request, you’re using the wrong protocol or port, or a Docker port mapping is incorrect. Check your terminal for errors and try the direct address.

Will ERR_EMPTY_RESPONSE go away on its own?

Sometimes, if it was caused by a short server restart or glitch. If a crashing plugin, bad configuration or firewall rule is the cause, it will keep coming back until you fix it.

Does ERR_EMPTY_RESPONSE hurt SEO?

Brief outages usually don’t, but long or repeated ones can reduce crawling and may remove pages from the index. Fixing the problem quickly keeps the damage small.

Final thoughts

ERR_EMPTY_RESPONSE feels vague because the server gives you nothing to work with, but that silence is itself a clue. For visitors, it usually comes down to cookies, extensions, a VPN, antivirus software or DNS.

For site owners, it’s most often a crashing PHP process, a bad plugin or theme, a broken config, or a firewall or proxy that’s eating the response.

Start by finding out whether the problem is local or global, reproduce it with curl, and follow the logs. Those three steps solve most cases.