ERR_EMPTY_RESPONSE: Fixes for WordPress Sites and Browsers

Key Takeaways

• The ERR_EMPTY_RESPONSE error indicates a complete lack of a response from the server, making it tricky to diagnose because there’s no error code to guide you.
• Fixes for this error fall into two main categories: client-side issues (like a bad network connection, corrupt cache, or browser extensions) and server-side issues (like a server crash or a plugin/theme conflict on a WordPress site).
• Troubleshooting this error requires a step-by-step process of elimination on both the browser and the server to identify the specific root cause of the broken communication.

You ever click on a site—maybe your own WordPress blog, maybe just some random page—and instead of loading, it just spits back that little line: ERR_EMPTY_RESPONSE. No clue, no explanation. Just that.

Honestly, it feels broken in the worst way because nothing is telling you what’s wrong. If it’s your site, you’re probably thinking, “Great… how many people have been staring at this instead of my page?” And if you’re just browsing, well, it’s equally annoying—you hit refresh three times like it’s going to magically fix itself.

What’s happening here isn’t as dramatic as it looks. In plain English, your browser asked the server for something, and the server gave… nothing. Zero response. And yeah, that’s as unhelpful as it sounds.

The good part?

It’s not as complicated as it looks. In this guide, we’ll walk through the most common causes and fixes so you can get things working smoothly again.

What the ERR_EMPTY_RESPONSE Error Means

When you hit this error, your browser did send a request to the server — but the server never sent anything back. No HTML, no headers, not even an error message. Essentially, it’s a zero-byte response.

In practice, this can look a few different ways. Chrome usually shows “No data received” or “This page isn’t working.” Firefox or Edge might phrase it differently, but the root issue is the same: your browser is left waiting for data that never arrives.

That silence is the part that makes it tricky. With a 408 request timeout error, you at least know the server is slow. With a 500 error, you know something went wrong on the backend. But with ERR_EMPTY_RESPONSE, there’s nothing to go on — which means you have to investigate both sides.

Sometimes the problem is on the server (PHP crashed, Nginx dropped the connection, firewall rules misfired). Other times, it’s on your end (unstable network, bad browser extension, or even a VPN cutting the response).

So while the error looks simple on the surface, it’s really just the browser telling you: “I asked, but I got nothing.”

Common Causes of the ERR_EMPTY_RESPONSE Error

The tricky part about this error is that it doesn’t point to one single issue. Instead, it usually happens when the usual exchange of data between your browser and the server gets disrupted. A few of the more likely culprits include:

• Unstable internet connection – a very brief disconnection in your network could stop data in its tracks and block the response out.
• Server-side issues – the server could be overloaded, configured incorrectly, or sometimes simply down for temporary maintenance. Whatever the reason, the server could just stop running before responding.
• Corrupt cache or cookies – while browsers do have caches to speed up loading sites quickly, broken data based on what is in cache or stored cookies may be blocking the server response.
• Extension interferences – certain add-ons you may have on your browser (like ad blockers or privacy tools) could be doing their job too well and are blocking your connection.
• Firewall or antivirus filters – security tools can be overprotective, cutting off requests that are actually safe.
• Damaged temporary files – if there is a glitch somewhere within local system files, it may keep your device from completing the request.

Attributing to the fact that the error itself does not indicate which one is the real culprit, you’ll need to rule them out step by step. Next, we’ll look at how both everyday visitors and WordPress site owners can start troubleshooting to fix this error.

How To Fix the “ERR_EMPTY_RESPONSE” Error

Now it’s time we take a look at several tried-and-tested fixes to resolve the ERR_EMPTY_RESPONSE error. To make things easier, we’ve separated the steps for everyday visitors and for WordPress site owners.

Fix ERR_EMPTY_RESPONSE Error for Regular Visitors

If you’re just trying to access a site and run into this error, start with the basic troubleshooting steps below. These don’t require technical knowledge and often clear up the issue quickly.

1. Make Sure Your Connection Is Stable

As I said earlier, this error can trigger when your internet drops, even for just a second. If the browser can’t keep the line open, it ends up with nothing to show. An easy way to test is by trying another connection — switch from Wi-Fi to mobile data, or plug your device directly into the router. If the page loads fine elsewhere, you’ve found the weak link.

2. Test the Site in Private Browsing Mode

Your browser stores cached files, cookies, and other session data that can sometimes interfere with how pages load. Opening the site in Incognito (or Private Browsing) mode gives you a clean slate — no saved cache or extensions running by default.

If the site works there, it’s a sign that something in your regular browser setup is causing the error, and you’ll know to clear cache or check extensions next.

3. Test Your Browser Without Extensions

Extensions can quietly interfere with how your browser talks to a website. For example, an ad blocker might cut off scripts a site needs to load, or a security add-on could mistake safe traffic for something suspicious. When that happens, your browser’s request goes out, but the response never makes it back — triggering the ERR_EMPTY_RESPONSE error.

In Chrome:

• Click the three-dot menu in the top right.
• Choose Extensions > Manage extensions.

• Then disable all extensions.

• Now reload your site again. If the page loads, you’ve confirmed one of the extensions is the culprit. Turn your extensions back on one at a time until the error shows up again—this way, you’ll know exactly which one to remove or replace.

4. Clear Out Old Cache and Cookies

Your browser stores bits of data from every site you visit so pages can load faster next time. But over time, these files can become outdated or corrupted, causing connection errors like ERR_EMPTY_RESPONSE. Wiping the cache and cookies gives your browser a fresh start.

If you’re using Chrome, go to Settings > then Privacy and security, then Delete browsing data. I usually pick “All time” just to be thorough. Make sure “Cached images and files” is ticked, then clear it out.

Once cleared, try reloading the site — if it works, you’ll know the old stored data was blocking the response.

5. Clear (Flush) Your DNS cache

Your computer keeps a small record of the sites you visit, called the DNS cache. It’s meant to speed things up, but when those records get outdated or corrupted, they can break the connection between your browser and the website — sometimes leading to the ERR_EMPTY_RESPONSE error.

Flushing the DNS cache forces your device to fetch fresh records.

• On Windows, click the Start button, type cmd, right-click Command Prompt, and pick Run as administrator.

• Type this: ipconfig /flushdns.
• Hit enter and you should see this message: Successfully flushed the DNS Resolver Cache.

• On macOS, just open up Terminal.
• Paste this line: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
• Press enter, then enter your password when prompted.

Once done, try reloading the site. If cached records were the problem, it should work right away.

6. Reset Network Settings

If clearing the DNS cache didn’t do the trick, the issue may run deeper in your network configuration. Over time, your computer builds up a set of temporary network settings that can become misconfigured or corrupted.

Resetting them forces your system to create fresh connections, often fixing errors like ERR_EMPTY_RESPONSE.

Here’s how you can reset network setting for Windows and macOS:

• On Windows, open the Start Menu, type cmd, right-click Command Prompt, and choose Run as administrator.
• Type these commands one by one, pressing Enter after each:

ipconfig /release

ipconfig /all

ipconfig /flushdns

ipconfig /renew

netsh int ip set dns

netsh winsock reset

• Once they finish running, close the window and restart your computer.
• On macOS, open System Preferences → Network.

• Select your active connection (Wi-Fi or Ethernet), then click Advanced → TCP/IP.
• Hit Renew DHCP Lease to refresh your network details.
• Restart your Mac for good measure.

After the reset, open Chrome (or any browser) and try loading the site again. If the error was tied to bad network data, it should now be gone.

Don’t Let Errors Slow You Down

With reliable WordPress hosting, you won’t have to deal with frustrating issues like “ERR_EMPTY_RESPONSE.” Keep your site fast, stable, and always available.

TRY NOW

Fix ERR_EMPTY_RESPONSE Error for Website Owners

If you own or manage multiple WordPress sites and your visitors are seeing this error, the cause might lie in your site’s setup or hosting environment. The following methods will help you identify and resolve server-side issues.

1. Fix Plugin Conflicts

Sometimes a faulty or outdated plugin can break the communication between your site and the browser, leading to the ERR_EMPTY_RESPONSE error.

To troubleshoot, try disabling your plugins. Now, you can do this one by one or through bulk actions. Let’s go with bulk actions to save time.

To do this:

• Head over to your WordPress dashboard.
• Click on “Plugins” in the sidebar menu like above.

• In the top left corner, there’s a checkbox next to all the plugins. Tick that box to select them all.

• Now select the “Bulk Actions” option. You’ll see a bunch of options. Choose “Deactivate.”

• Hit the “Apply” button. All your plugins will now be deactivated.

In some cases, this error can lock you out of both your website and the WordPress dashboard. If that happens, you won’t be able to deactivate plugins the normal way. In such a case, you can still do it through FTP or your hosting file manager.

Let’s see how you can use an FTP client like FileZilla to access your website’s files:

• Log into your server using FileZilla. If you’re a Cloudaways user, you can find your credentials in Server Management > Master Credentials.

• Navigate to the wp-content folder in your site’s root directory.

• Find the plugins folder and rename it to something like disabled_plugins.

• Check your website. If it loads, you’ve confirmed that a plugin is the problem.
• To find the exact culprit, rename the folder back to plugins, then rename each plugin folder one at a time (e.g., rename contact-form-7 to contact-form-7_disabled), then reload your site. When the site starts working again, the last plugin you disabled is the one you’d want to delete or update.

2. Rollback to a Default WordPress Theme

Sometimes it isn’t a plugin at all — your WordPress theme can be the reason behind the ERR_EMPTY_RESPONSE error. A poorly coded function, outdated files, or a conflict with a recent WordPress update can all break the connection.

To check if your theme is causing the issue:

• To test this, open your WordPress dashboard and go to Appearance → Themes. Activate one of the default or hybrid WordPress themes (like Twenty Twenty-One or Twenty Twenty-Three).

• Once you switch, refresh your site to see if the error is gone. If it is, your previous theme was likely the cause.

If you can’t log in through the dashboard, you can still test this by using FTP (or your host’s file manager).

Here’s how:

• Just like I showed you earlier, connect to your site via FTP and open the /wp-content/themes/ folder.
• Find the folder for your active theme and rename it — for example, change mytheme to mytheme_old.

• WordPress won’t find that theme anymore, so it will automatically fall back to a default theme like Twenty Twenty-One (or whichever default you have installed).
• Now reload your site. If it works, your theme is the culprit, and you’ll know it’s time to either update it, contact the theme developer, or switch to a better-maintained theme.

• If the error persists, your theme isn’t to blame, and you can rename the folder back to restore it.

This step is less about permanently changing your site’s look and more about ruling out whether the design layer is part of the problem.

3. Verify Your Database Connection

If your WordPress site can’t talk to its database properly, you may run into errors like ERR_EMPTY_RESPONSE because the server can’t deliver the information your browser is asking for. This usually happens when database credentials in your configuration file don’t match what’s actually set on your hosting server.

Here’s how you can check and fix it:

• Connect to your site using FTP or your hosting file manager, then locate the wp-config.php file in the root directory.

Look for these lines:

define( ‘DB_NAME’, ‘your_database_name’ );

define( ‘DB_USER’, ‘your_username’ );

define( ‘DB_PASSWORD’, ‘your_password’ );

define( ‘DB_HOST’, ‘localhost’ );

• Match them with your hosting details. Log in to your hosting control panel and confirm your database name, username, password, and host address. If anything looks off, update it in wp-config.php and save the file.
• Don’t forget DB_HOST: While most hosts use localhost, some use a specific hostname or IP address. Check your hosting documentation if your site still won’t connect.
• Test your site: Refresh your browser and see if the error disappears. If not, you may also need to reset the database user password in your hosting panel and update it in wp-config.php.

4. Increase the PHP Memory Limit

If your WordPress site doesn’t have enough memory to process requests, it can break the connection between the browser and the server — sometimes showing up as an ERR_EMPTY_RESPONSE error. This often happens with bulky plugins, heavy themes, or spikes in site traffic.

Here’s how you can increase your PHP memory allocation:

Option 1: Edit wp-config.php Manually

• Connect to your site via FTP or your hosting file manager.
• Open your site’s root directory and download the wp-config.php file.

In a text editor, add this line just above:

/* That’s all, stop editing! Happy publishing. */

define( 'WP_MEMORY_LIMIT', '256M' );

Save the file and upload it back to your server.

If 256M doesn’t help, try 512M or 1024M — but note that you can’t exceed the hard limit set by your hosting provider.

Option 2: Adjust Memory Limit on Cloudways

If you want an easier solution, without tweaking the wp-config.php via FTP, Cloudways users can increase the PHP memory limit directly from the platform by heading to Settings & Packages > Memory Limit.

Once updated, check your WordPress site to confirm whether the ERR_EMPTY_RESPONSE issue is resolved. If not, move to the next solution.

5. Reach Out to Your Hosting Provider

If you’ve worked through all the fixes and the ERR_EMPTY_RESPONSE error still won’t go away, the issue might be deeper—something on the server side that’s beyond your control. In that case, the smartest move is to get in touch with your hosting provider. Their support team can dig into server logs, firewall rules, or misconfigurations that you won’t be able to access on your own.

Cloudways offers 24/7 live chat support, so you can connect with a real person right away. Whether it’s a server-level conflict, database hiccup, or PHP limit issue, their team can quickly identify what’s wrong and guide you to a solution.

Wrapping Up!

The ERR_EMPTY_RESPONSE error might seem intimidating at first, but in most cases, it’s nothing more than a connection glitch.

In this blog, we walked through quick fixes like checking your connection, trying a private window, clear cache/cookies and stuff like that. For site owners, we covered disabling plugins, falling back to a default theme, raising the PHP memory etc.

Try different troubleshootings steps mentioned in this guide and you’ll be able to pin down the culprit fast.

If you’re hosting on Cloudways, you’ve got an extra edge. Tasks like increasing PHP memory or resetting configurations are much easier to handle, and if you ever get stuck, our support team is available 24/7 to guide you through it.

If you have any questions, let us know in the comments below.