Random 500 Internal Server Error (godaddy)

Thanks for the update. Your last error log gives a ‘Premature end of script headers’ error, then references your index file. This tells us that a script in your index file is responsible for your 500 Internal Server Errors. Unfortunately, there is not a simple fix for this one as the error is just saying that something didn’t work. Like James (MacManX) mentioned, the error is likely related to a plugin. Try backing up your plugins folder, then deleting them completely and see if the same error occurs.

Let us know how it goes!

Alicia
GoDaddy.com

I’m having the exact same issue with random Server 500 errors running a WP blog on GD shared Linux hosting.

SAME experience with their phone tech support as well. They told me that it must be a WordPress issue and that I was on my own and should debug the WP scripts! Also tried to upsell me to hosting plan where I can access the logs, but I’m refusing – shouldn’t have to pay more to a company if they aren’t helping to solve a issue that **potentially could be due to their server config, etc.**

If I deactivate all plugins I still get the error. Again, randomly and somewhat infrequently.

I’m pretty close to asking GD to move me to another server, and then moving off of GD if we can’t get this to work.

I should note that my website takes under 5 seconds to load normally. However, once in a while things get very slow and the server throws the 500 errors. This is random – I cannot reproduce it on particular pages, or with particular steps, or with particular plugins activated.

Anything resolved for folks on this? I’ve got the same issue. The minute I think it is resolved, I try again and have it back like a bad penny.

The last change I made is to make sure and chmod everything that is WordPress/PHP-related 755 (executable). So far so good, but I’m not counting my chickens just yet. ??

Chickens counted. I think the chmod did it.

Not. Didn’t resolve it.

Well I’m getting the same issues, “premature end of script headers” error.
I have deluxe hosting at godaddy and I also have quiet a few plugins installed.
So in order to test it with no plugins I’ve installed another wordpress system under different subdomain and different MYSql and no plugins at all, just clean install of the wordpress an problem is happening also on the clean install.
The full blog is blog.udiburg.com and the test one is staging1.udiburg.com.

Godaddy team,
Would you consider better support on this? Cause it looks like it has nothing to do with the WordPress but with the combination of WordPress on godaddy.
This doesn’t happen on another hosting or on a dedicated Linux server I’ve installed in my lab.

Hey 007me… no resolution for me either. My client plans to upgrade from economy hosting to deluxe just so I can see what the error log looks like. Until then, because it is a predictably sporadic problem, they haven’t seen it and so therefore it doesn’t exist.

The symptom I see looks like some kind of database/web server latency. If the web server hasn’t spoken with the DB server in some time, it throws the error. Refresh and everything is fine!

Thinking about moving to a different hosting provider — on my own development site, which is also shared hosting, it worked with no problems.

-Chuck

Well, it looks like godaddy doesn’t care if their clients will move to another hosting cause they have so many customers.
I’m running a ticket for 2 days now with them with no help.
they keep telling me that it’s a WordPress issue.

Any further word, 007me? What’s interesting is that your test blog produced the same results. That pretty much rules out the problem being with WordPress, I would think.

BTW, I went to your staging blog and the live one and didn’t see any errors at all, but as we know this is a random issue. I had found with my testing that the error seemed to occur more when I turned OFF database caching. I’m using a plugin called “hyper-cache,” and with it turned off errors occurred with greater frequency, which leads me to believe the issue is some kind of network latency between the web server and database server.

Cewyattjr, as you know it’s random, and if you will try each blog few times you’ll see the error.
I’m using now super-cache plug-in and now I have less errors, so I must agree with you that the problem is on Godaddy side.
Their support finally answered me and said that because I installed the WP manually I have all the errors and that I should use their Auto WP install.
But, they are providing the auto install with PHP4.2 instead of PHP5 and many plug-ins need the PHP5 in order to work.
Big mess with Godaddy.

I was wondering how the “auto install” would work, and disappointing that it is only PHP 4.2. I imagine I have the issue that certain plugins need PHP5.

Would be interesting to test… Do you happen to know where it is in the GD configuration that selects PHP 4 versus PHP5? I looked in .htaccess for my current site with the issues and another one with their auto install and don’t see any PHP5 cgi version selected with either.

Thanks so much!

Well, they just sent me instructions how to change the PHP:

Be aware that the PHP version on the account is related to the option which you selected when creating the plan. Our system does not automatically select a version of PHP to use when you install an application through our Hosting Connection interface. If you wish to change the PHP version, you can do so by following these directions:

1. Log in to your Account Manager.
2. From the Products section, click Web Hosting.
3. Next to the hosting account you want to use, click Launch.
4. In the Content section of the Hosting Control Center, click the Add-On Languages icon.
5. Select the PHP version you want to use.
6. Click Continue.
7. Click Update.

I’m seeing a 500 internal server error as well but it only appears in the admin area.

It seems to be a clash between All-In-One-SEO-Pack and Tubepress.

If I deactivate all plugins and begin reactivating them one by one, once Tubepress is activated everything works until all-in-one-seo is activated.

I’m currently still looking for a solution.