Title: Issue with WordPress going unresponsive Last modified: August 21, 2016 --- # Issue with WordPress going unresponsive * [CraigI](https://wordpress.org/support/users/craigi/) * (@craigi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/) * I just recently moved to 3.6 and seem to be getting a lot of issues to where the entire site goes unresponsive. It seems as though it’s related to whenever I’m making actual changes to widgets, themes, plugins, general posting etc that when the issue comes up. * I do not get much in the way of Chrome giving me an error except that I get a“ ERR_EMPTY_RESPONSE.” The issue can easily be reproduced by using a text widget and clicking save a few times and then boom the site goes down. * In some cases the entire site goes down but others I am still able to access the main page and click on posts. Other times it is completely down for 30 seconds to a minute. * The Apache logs show the following each time the crash happens. * [Thu Aug 08 14:32:27 2013] [6289570] [fcgid:warn] (20014)Internal error: [client xx.xx.xx.xx:63857] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function * So far I have disabled every plugin and moved to the default theme and still get the same issue. This WordPress instance is hosted on GoDaddy. * Anyone seeing this type of issue or can help point me in the right direction in finding a solution? Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/page/2/?output_format=md) [→](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/page/2/?output_format=md) * [Siobhan](https://wordpress.org/support/users/siobhyb/) * (@siobhyb) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012264) * Hey. * I found a few threads from over the past week where people seemed to be experiencing the same issue: * [http://wordpress.org/support/topic/failed-installation-with-error-code-err_empty_response?replies=8](http://wordpress.org/support/topic/failed-installation-with-error-code-err_empty_response?replies=8) [http://wordpress.org/support/topic/error-324-neterr_empty_response-the-server-closed-the-connection-without-se/page/2?replies=76](http://wordpress.org/support/topic/error-324-neterr_empty_response-the-server-closed-the-connection-without-se/page/2?replies=76) * And from the Go Daddy forums: * [http://support.godaddy.com/groups/web-hosting/forum/topic/error-code-err_empty_response/?topic_page=2&num=15](http://support.godaddy.com/groups/web-hosting/forum/topic/error-code-err_empty_response/?topic_page=2&num=15) * Someone else on those threads detailed the following steps that fixed the issue for them: * > I was able to fix the same problem that was happening to my site. > 1. Close > your browser and delete all cookies/cache just in case. 2. Open the FTP client > and log into your website’s root folder. 3. Download and save the “.htaccess” > file into your desktop. 4. Delete the .htaccess file from your webroot folder > then press the reload button on FTP client to make sure the .htaccess is gone. > 5. Open your website and refresh the page few more times. Try to log in. It > should work now! It worked for me. 6. Put the SAME .htaccess file back to your > site’s root folder.Wait few seconds and refresh FTP to make sure the file is > there and it has at least -rw—-r– permissions. 7. Open your website,refresh > the page, try to log in.You SHOULD be able to log in with the SAME .htaccess > file that was causing the problem earlier. * Thread Starter [CraigI](https://wordpress.org/support/users/craigi/) * (@craigi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012357) * I’ve tried what Siobhan suggested with no luck. Removing the .htaccess and logging in after clearing the browsers cache still results in crashes. I did read over the other posts and not really finding any additional help. Keep the suggestions coming because I’m still not finding much that is resolving my issue. * Thank you so far! * [WPyogi](https://wordpress.org/support/users/wpyogi/) * (@wpyogi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012364) * Have you contacted GoDaddy? * Thread Starter [CraigI](https://wordpress.org/support/users/craigi/) * (@craigi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012410) * Absolutely and they say it’s not a server issue and that I need to troubleshoot my code. * [viniciuswerneck](https://wordpress.org/support/users/viniciuswerneck/) * (@viniciuswerneck) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012474) * I’ve contacted Godaddy as well and they told me the same thing: it’s an internal wordpress problem and they can’t do anything. That I should seek help here. ** My log is exactly the same as Craigl’s. ** * [viniciuswerneck](https://wordpress.org/support/users/viniciuswerneck/) * (@viniciuswerneck) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012475) * It also started after upgrading to WordPress 3.6. * [user505](https://wordpress.org/support/users/user505/) * (@user505) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012499) * Hello, I’m the user that Siobhan mentioned and I thought my problem was fixed by removing the .htaccess file but I still get the same error and the exact error that Craigl posted on his first post is reported in my Error Logs folder too. My host is GoDaddy as well and they told me that it’s a problem related to my website’s code but that is simply not true.I don’t run WordPress by the way.It’s a PHP based CMS with integrated phpbb forums. Last week I was completely locked out of my website.It would not even load the homepage but other users had no problem at all.I contacted GoDaddy and they acknowledged that it was a problem related to their recent Apache update.They upgraded it to 2.4 and I believe they have modified ModSecurity settings. * THE PROBLEM: happens in different scenarios. 1)When I use a PHP tool to enter data into a MySQL database.After entering 3-5 times (in less than 10 minutes??) I get a response “Connection Reset” on FireFox and “ERR_EMPTY_RESPONSE” on Chrome. 2) When I edit the forum post 3-4 times. 3) When I use the forum’s admin panel to modify user related permissions .I get locked out again for 2-5 minutes. * This is a GoDaddy side problem.Their forums were flooded with people reporting the same thing.Earlier today they told me to disable FastCGI and use CGI instead. I added the following lines in .htaccess but that didn’t help: * addhandler x-httpd-php-cgi .php4 addhandler x-httpd-php5-cgi .php addhandler x-httpd-php5-cgi .php5 * That is all I have in my htaccess file.Try that and see if it works for you. * [user505](https://wordpress.org/support/users/user505/) * (@user505) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012514) * The problem was solved on my website.Nothing was wrong with my web code and nothing is wrong with your WordPress setup.There is nothing you can do on YOUR side to fix this. I contacted their tech support and asked them to whitelist my IP address in their ModSecurity settings so I won’t get flagged as a spammer.Now I don’t get the blank page anymore.It is the ModSecurity that thinks you are a spambot after adding or modifying few things in 1-2 minutes.I think their security settings are way too strict. Hopefully your IP is static or at least a cable connection so it doesn’t change the addresses after every modem reboot. Good luck ! * [Siobhan](https://wordpress.org/support/users/siobhyb/) * (@siobhyb) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012523) * Hi user505: Thanks so much for finding my post and replying here! I’ve also asked some of the mods here about this problem, and the general consensus seems to be that it’s down to GoDaddy’s ultra-strict security settings. * Craigl + viniciuswerneck: Could you try asking GoDaddy to add you to their whitelist? * [allklier](https://wordpress.org/support/users/allklier/) * (@allklier) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012526) * I think what user505 is spot on. I’m still working with GoDaddy on my site that is experiencing the problem, but the symptoms did speak to a security filter that is too strict. * In my case the code can make a series of POST requests in a short time period. It wouldn’t fail on every call, or even on the same one. But once a call failed, they would all fail for several minutes out. I modified the code to retry a call, both immediately or with a delay. No improvement. * It clearly looks like a security filter that sees a burst of suspicious activity, particularly POST requests on https: sites and then blocks all further requests for a time. Makes sense, as that pattern is what you would see if a script tried to guess passwords on a login page. But there are legitimate sites doing these kind of requests, so the filter is a bit to simple the way it’s setup. * Thread Starter [CraigI](https://wordpress.org/support/users/craigi/) * (@craigi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012527) * I was under a self imposed timeline of getting my site back up and running and it really looked like no resolution was going to be found in the near future. My fix was [here](http://it-erate.com/resolution-godaddy-wordpress-issues/). Boiled down, I moved to a different WordPress provider. * No fault against GoDaddy though as their expertise doesn’t reside in WordPress. I still like GoDaddy and will still use them for other things; just not WordPress hosting. * I would really like to still hear about if anyone finds a resolution, please keep posting as anything is found out. * [allklier](https://wordpress.org/support/users/allklier/) * (@allklier) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012528) * Craigl, that is a reasonable solution if you are under deadline. Just be aware that this problem has nothing to do with WordPress. The pattern that is being filtered against here can come from any type of software. The code in question on my site is custom code that has nothing to do with WordPress. And if you host another site that makes a series of POST requests on https connections it may fail as well. * This is a hosting provider configuration issue from what we know so far. Not to their fault – they deal with a lot of sites that get attacked and they need to be proactive about it, but it requires a bit more fine tuning obviously. * Thread Starter [CraigI](https://wordpress.org/support/users/craigi/) * (@craigi) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012529) * Understood Allklier and I’m hoping they get this figured out soon. Up until now based on my talks with GoDaddy they made it sound (to me at least) that it was WordPress related. Certainly a good point that this is not just a WordPress issue. * [allklier](https://wordpress.org/support/users/allklier/) * (@allklier) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012530) * Absolutely. I’m sure they get a lot of support requests that end up client software related, and given the variety of sites they deal with, it would be a mammoth task to be able to diagnose these all the time correctly. So they default to the ‘it’s your code’ answer unless they have clear evidence to the contrary. * Your best bet is to do your homework and provide as much specific data about the scenario as well as a way to reproduce it when you contact them. * In this case, the error logs and an internal Apache error message was the clue. No client code problem can cause internal Apache error messages. If you have that evidence on hand, it’s on them. * [viniciuswerneck](https://wordpress.org/support/users/viniciuswerneck/) * (@viniciuswerneck) * [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/#post-4012532) * Thanks for the info, guys! When I called GoDaddy they insisted the issue was on my side, even with the error log. I’ve tryed argumenting but they kept saying: check your codes. And I found nothing wrong. Adding the 3 calls I had, I’ve stayed with them more them 3 hours on the phone. Still, no solution. Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/page/2/?output_format=md) [→](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/page/2/?output_format=md) The topic ‘Issue with WordPress going unresponsive’ is closed to new replies. ## Tags * [gnome-opw](https://wordpress.org/support/topic-tag/gnome-opw/) * [godaddy](https://wordpress.org/support/topic-tag/godaddy/) * [internal-error](https://wordpress.org/support/topic-tag/internal-error/) * [mod_fcgid](https://wordpress.org/support/topic-tag/mod_fcgid/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 21 replies * 6 participants * Last reply from: [allklier](https://wordpress.org/support/users/allklier/) * Last activity: [12 years, 10 months ago](https://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive/page/2/#post-4012595) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics