Let’s take a look on the ‘err_empty_response’ on Apache and the ways to fix it. At Bobcares, we offers solutions to server issues as part of our Server Management Services.

Need to know more? Continue reading and get in touch with us if you have any further inquiries.

ERR_Empty_Response: The website didn’t send any data, and might be down

ERR_EMPTY_RESPONSE: The website didn’t send any data, and might be down / ERROR 324 ( net:: ERR_EMPTY_RESPONSE ) appears when we try to access a website and the website isn’t responding or sending any data to our requests. The error appears on various browsers including Mozilla Firefox, Google Chrome, Internet Explorer, etc.

How To Fix ERR_Empty_Response?

We have outlined some of the methods to fix the error for you.

1. Using Command Prompt

1. Open the command prompt as admin and execute the following commands:

   To Reset Network stack:

   ipconfig/release
   ipconfig/all
   ipconfig/flushdns
   ipconfig/renew

    

   To Reset Winsock:

   netsh int ip set dns
   netsh winsock reset

    
2. Now restart the system and reload the page.

2. By Changing The DNS Settings

1. Firstly, right click on the Network Icon.
2. Then click on Open Network and Sharing Center.
3. Click on the Change Adaptor Settings option.
4. Now select and right click on the network, and choose Properties.
5. Select Internet Protocol Version 4 ( TCP/IPv4) and click on Properties.
6. Choose Use the following DNS server address from the available options and then add Preferred DNS Server: 8.8.8.8 and Alternate DNS Server: 8.8.4.4.
7. Now clear the browser DNS cache (Google Chrome)
8. Open Google Chrome and type chrome://net-internals/#dns.
9. Click on the drop-down icon at the top right side of the browser.
10. Click on Clear Cache & Flush Sockets. Thus we can fix err_empty_response.

3. By Adjusting Browser Settings

If the problem is with a web browser, we must do the following measures to resolve the err_empty_response.

1. First of all, try reloading the page.
2. Else, ensure there is no issues with internet connection. After that, try reloading the tab with error.
3. Then try clearing the cache. Then try reloading the tab with the error.
4. Also close other tabs, extensions, & apps and try reloading the tab with the error.
5. Restart the Computer and reload the tab with the error.
6. Find and remove unwanted software and try reloading the tab with the error.
7. Check for Browser Updates. After the update, relaunch and try reloading the tab with the error.

4. By Changing The wp-login.php

If the error appear only when we try to log in then the problem is with the wp-login.php, then we have to replace the wp-login.php file with the latest application file.

ERR_Empty_Response on Apache

Now let’s see how our Support team assisted one of our customer in fixing the err_empty_response error on local Apache setup. While developing a web app locally which makes API calls, the user notices some of the API calls have suddenly stopped working, while others continue to work. If the user go directly to an api endpoint in the browser, the first time it always returns:

This page isn’t working
samplesite.com didn’t send any data.
ERR_EMPTY_RESPONSE

An error appears in the Apache log.

[Mon Jan 20 22:10:18.133644 2020] [core:notice] [pid 4702] AH00052: child pid 6191 exit signal Segmentation fault (11)
[Mon Jan 20 22:14:02.343396 2020] [core:notice] [pid 4702] AH00052: child pid 6241 exit signal Segmentation fault (11)
[Mon Jan 20 22:14:02.343886 2020] [core:notice] [pid 4702] AH00052: child pid 6240 exit signal Segmentation fault (11)
[Mon Jan 20 22:14:07.349923 2020] [core:notice] [pid 4702] AH00052: child pid 6212 exit signal Segmentation fault (11)

The user tried many ways to fix err_empty_response on Apache such as restarting Apache, clearing browser cache, making the request in incognito mode, using various browsers and so on. However, none of these appears to have resolved the problem.

Our Support team finds reading the error in Firefox provided a bit more of a clue. Firefox’s error said:

Secure Connection Failed: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified

So for some reason there is an SSL problem. The user had locally created a self-signed SSL certificate for testing (supporting wildcard subdomains). However, it had not expired. Now let’s see the solution which solves the issue.

Solution: We suggested to not use https locally and update the .htaccess files to only force https on the live site (mysite.com) and not the dev site (mysite.test):

RewriteEngine On

RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_HOST} mysite.com$
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, our Support team went over the err_empty_response details, along with the solution for err_empty_response on Apache setup.