ERR_EMPTY_RESPONSE

hayesmd
(@hayesmd)

10 years, 8 months ago

We receive the ERR_EMPTY_RESPONSE error anytime we try to save/publish a post/page that contains more than 10-15 links within it.

I am on Go Daddy hosting. We have about 8 WP sites in our account and they all exhibit the same behavior. For us there are 2 methods to reproduce the error.

1) Clicking around the Admin screens too fast triggers the error.

2) Saving/Publishing a post or page that has more than 10-15 links within it.

The logs say there were too many internal redirects and it’s cuts us off for 60 seconds. When this happens I can pull up a 404 error log and the admin-ajax.php gets flagged as 404. My assumptions are that that file is doing something with the content of the post, checking links or something and is being flagged by Go Daddy’s mod_security file for internal redirects and it shuts us down.

Go Daddy is saying it is nothing with their system. The hosting account does what it should and that the problem is within the code. We have tried all the basic troubleshooting, disabled all plugins, changed to default theme, increases memory to 96mb via php5.ini and increased the timeout to 180 via php5.ini.

Here is the URL of the site that we have been testing on, but it is present in all of our WP 3.6 installs in the account.

learning2coupon.com

Here are a list of the common Apache errors we are seeing in our logs.

End of script output before headers: index.php

mod_fcgid: read data timeout in 120 seconds, referer

mod_fcgid: ap_pass_brigade failed in handle_request_ipc function,

Thank you,

Viewing 15 replies - 1 through 15 (of 26 total)

1 2 →

graphical_force
(@graphical_force)

10 years, 8 months ago

All you can do is disable all plugins and then try the default theme to see if you still have an issue. If you do then you know that it is with the hosting. A lot of people seem to be having issues with Godaddy’s hosting and wordpress.

Thread Starter hayesmd
(@hayesmd)

10 years, 8 months ago

We already tried that. Didn’t resolve the issue. Go Daddy’s stance was the hosting account works and is sending pages. The error is within the code being sent. In this case it looks like an internal core file of WP.

They did at least admit that it is their new mod_security file that is kicking out the IP for 60 seconds after more than 10 redirects occur within so many seconds.

They also said the mod_security was upgraded recently due to the recent bot attacks that took place in Jun-Jul.

graphical_force
(@graphical_force)

10 years, 8 months ago

I’m very curious to see if you still had those issues if you were not on Godaddy’s servers. If you are saying that something is wrong with wp core, although it is a possibility it is pretty unlikely as to others not having that issue.

Maybe others can shed some light on it.

Thread Starter hayesmd
(@hayesmd)

10 years, 8 months ago

It does not occur on any other hosting provider that we’ve used. We recently purchased a WP site that worked fine until we transferred it to our Go Daddy hosting. We have 2 other WP sites on a separate host and they do not exhibit this problem either. Granted those 2 sites are 3.5 and our Go Daddy sites are 3.6.

We’ve actually copy/pasted the text of a post between the 2 spectate sites and hosts and the error only occurs on the Go Daddy hosted sites.

WPyogi
(@wpyogi)

10 years, 8 months ago

Yes, we’ve seen this in some other threads – also on GoDaddy – see:

http://wordpress.org/support/topic/issue-with-wordpress-going-unresponsive?replies=21

http://wordpress.org/support/topic/site-broken-connection-reset?replies=3

graphical_force
(@graphical_force)

10 years, 8 months ago

It sounds like you know what the issue is. I’ve not used godaddy for hosting but I know others have had issues with it. Maybe the correct answer is to move them?

Thread Starter hayesmd
(@hayesmd)

10 years, 8 months ago

Thanks, WPyogi, I’ll take a look at them:

Right now moving isn’t much of an option. The performance of the sites are blowing away our sites that are on a different host. We also pay more for those 2 sites hosted elsewhere than we do for 8 sites hosted on Go Daddy. We’ve also used 2 other hosts previously and had issues with the sites staying online.

Anyone know of a way to monitor exactly what goes on behind the scenes when a post is saved/published?

My theory is that WP is doing something with the content of the post and possibly validating all the links OR testing the rendered HTML, something and the Go Daddy mod_security is reacting to what’s being done within the browser most likely through the admin-ajax.php file.

PoX
(@pox)

10 years, 7 months ago

I have this exact issue with a wordpress site im building hosted by GoDaddy, i get this error when i have some media on pages such as a few png’s and publishing.

It is highly irritating.

*edit* O i forgot to add i use chrome browser on windows 7 64bit if that has anything to do with it.

klughaus
(@klughaus)

10 years, 7 months ago

Hello,

so glad that I found someone else with this same issue. It is very frustrating and I didn’t realize it’s because of all the internal links that’s causing this.

I guess as of now, there’s been no solution to this?

klughaus
(@klughaus)

10 years, 7 months ago

Been seeing the issue in all my browsers, chrome, firefox, safari, etc… so I don’t think it’s a browser issue.

Thread Starter hayesmd
(@hayesmd)

10 years, 7 months ago

For us on Go Daddy we resolved it by switching over to Windows Hosting. Like I said, that resolved the internal redirect issue since Windows uses IIS and not Apache. BUT, Windows hosting opened up a whole new can of worms. We eventually upgraded and went to a VPS solution with Linux where we could leave off the mod_security module and everything has been great ever since.

jmaybes
(@jmaybes)

10 years, 7 months ago

I have experienced the same problem for the past 3 months. At times much worst then others. I have spent the past 2 days on phone with support and this is their conclusion:
A few months ago they made ‘modsecurity’ changes to their servers to help prevent against bruteforce wordpress attacks. Well in making these changes they screwed many of us over by limiting the amount of post requests your site or IP can make at a given time -(the post requests can be theme related or plugin related as well which is why not EVERYONE with a wordpress site has these problems).If too many requests are sent, the site will crash out for a limited time. Now here’s the kicker, the only given fix is to upgrade to a dedicated server, costing you a ton more money, or you can run a VPN under your current, which is ridiculous to have to do. Keep in mind that they made these mod_sec changes without notifying any of us they were dong so, and people are still losing their minds trying to figure out the problem with their site.

The only REAL conclusion is to move hosting companies. Shame on you Godaddy.

Thread Starter hayesmd
(@hayesmd)

10 years, 7 months ago

At least they gave you the truth. I said I had read in forums that the above was the problem, but the reply I always got was there’s a problem with my code and since the hosting account is serving pages it’s not a server problem and that there was nothing they could do.

Oh, and for my first 3 weeks trying to figure it out they blamed it on my ISP, my browser, anything but changes they made. Even though multiple authors on our site could replicate the same problem. I even sent them some basic HTML that had 15-20 HREF’s in it and they never would try to create a post to see the issue for themselves even though their DEV’s created 2 WordPress installs in our account for testing purposes. They only ever posted ‘Hello World’ posts and not the HTML I sent them.

jmaybes
(@jmaybes)

10 years, 7 months ago

Oh, believe me, they did not want to give me the truth and still havent specifically admitted such. I am only so far able to confirm with the ‘bottom level help desk’. Its very intricate what I have been going through with them and only have learned what I have learned by talking to multiple persons there for help, whom in turn talk to others there, while I am on the phone.

I actually just got off the phone with some new help, while trying unsuccessfully to have my client IP whitelisted, and the person above him was denying mod_sec settings and trying to blame plugins. (Although I have been to the point of disabling all of them with the same problem occurring). When the problem occurs for me I not only lose access to the admin panel and such, I also lose access to just viewing the site from my IP, although it will pull up just fine from other IP’s. Whats happening is their mod_sec settings are blacklisting my IP when I try to send an update to the database, and the downtime lasts anywhere from 5-15min before repeating the cycle again. So if you are able to get godaddy to whitelist your IP then your problems should disappear, at least for the short term. I was not successful in getting them to whitelist mine, however, others have been. Whitelisting our IP is almost in fact admitting its the mod_sec changes and settings, which they do not want to do it seems.

So my first post is more of a hypothetical “this is the exact problem: statement.

Cheers.

Thread Starter hayesmd
(@hayesmd)

10 years, 7 months ago

Yep, exactly what we faced. I didn’t even push for whitelisting because we have 10 editors and maintaining their up-to-date IP’s would be impossible much less getting GD to update them for me.

As I said we were actually very successful running our WP sites through their Windows hosting and were even able to use WinCache successfully with W3T. We just had other permission type nuances pop up. Our decision to move to VPS was solely based on site growth. We also found out that GoDaddy shared hosting only supported 400 concurrent connections to all sites in the account. That could have been an issue for use during certain times a year. The VPS was a no-brainer.