Suffering with GoDaddy hosting downtime and"500 internal server error"

At this point with all the known data it is a 5% chance that it is a GoDaddy problem and a 95% chance that it is a problem specifically with this site.
Another thing you can do to troubleshoot this is to install another new WordPress installation in a new folder and then see what happens with that new site. If it is a Server problem then in theory this new site will also have the same problems.
Also you need to correct your custom php.ini file first and add the Zend Directives otherwise if this is all being caused because your custom php.ini file is not correct than the same problems will occur on the new WordPress installation. Or you could just take your custom php.ini file out of the mix altogether by renaming it for testing.

Yep. I was actually just thinking about doing that. I’ll get on that right now.

Site is inaccessible once again….

well remember when i mentioned to scan your site to see if it is hacked. It is hacked and you have at least one major coding problem. Chance that this is a GoDaddy problem is now 0%.
web site: greatgamingcrusade.com
status: Site infected with malware
web trust: Not Blacklisted
Site error detected.
Details: https://sucuri.net/malware/php-error-fatal-error
<b>Fatal error</b>: Call to undefined function the_uds_billboard() in <b>/home/content/xx/xxxxx/html/wp-content/themes/reviewit-theme/reviewit/index.php</b> on line <b>10</b>

Nope, that’s me messing around lol

I checked yesterday and mentioned that it was clean of malware and security issues.

ALso, removed W3 Total Cache and site is back.

Remember when I mentioned the whole Object Caching issue? I dug into the folders and found a leftover Object Cache file with cached items in it. Even if I have it turned off, can this leftover folder still cause issues?

oh. LOL Apparently that PHP Fatal error is happening to about 500 other websites too that are using that plugin. LOL Fatal error: Call to undefined function the_uds_billboard(). I’ll ping some those other sites to see if they have time out issues too. If W3TC caches a problem that already occured then you have cached the problem. ??

Ok i looked at 10 other sites that are showing this PHP Fatal error and using this plugin and the pings are coming back with time increases of around double or more, but no time outs so it just looks like this plugin causes huge resource drain, but is not causing time outs. it is possible though that W3TC is caching something about this plugin that is getting corrupted right away and then causing time outs. who knows for sure. Any way it has been an interesting adventure. good luck with all this. ??

I added that uBillboard plugin AFTER this started, so I doubt that’s an issue here.

Also, I still can’t help but still feel it’s GoDaddy as this was their end when it first started. They even said so, but then said that it was fixed. This was all about a week ago. Since they “fixed” the issue, I have been getting the error randomly. I don’t know. Site’s back down though, so not W3TC.

Thanks for helping AITpro

This is definitely NOT resolved yet.

Some Thoughts and Comments:

I have confirmed with GD Hosting Support that upon executing the upgrade to PHP 5.3, I was not only then at PHP 5.3 but was also ‘migrated’ to an upgraded data center area for 4GH with PHP 5.3 IIS7. My WP sites are all responding much better at all tasks now! (I also host ASP.NET sites so best of both worlds for me and my current and hopefully future customers).

Talk to GD about this as 5.3 is available on Linux accounts once the migration is complete (it was required for IIS7/PHP 5.3 web hosting and completed by GD without further interaction by me).

No help from GoDaddy by phone… wow

Again – the Zend Optimizer does not work on PHP 5.3 yet. The code has not been compiled yet. You need to run PHP 5.2.x in order to use the Zend Optimizer. This only applies in cases where you are personally doing advanced website configuration or advanced security measures so if you are just doing default stuff with your hosting account then yeah use PHP 5.3.

@aitpro,

Zend says use Zend Guard Loader (Runtime for PHP 5.3).

Release Notes

Are you saying this release is not to used?

And, yes, we are talking about a shared web host environment in this topic.

well if you want to use Zend Guard then sure yeah you would use 5.3. The choice is up to you. Since you are using Windows hosting then things may be different for what works best for your OS and WP. I have tested both and I’m sticking with 5.2.x and Zend Optimizer with WP until 5.3 does everything i want and performs as well as 5.2.x with Zend Optimizer on Linux hosting with WP.

Found another thread with these issues and W3 Total Cache. They told me over there that the plugin has a bug where it generates improper code in the htaccess file. The plugin sometimes will generate it’s code BEFORE the BEGIN/END wordpress code, and this is wrong. It should always be AFTER the wordpress code. Also, occasionally the code generated by W3TC has a few instances of its own BEGIN and END code and sometimes the instances between the first and last BEGIN and END doesn’t include the needed ‘#’. I checked in my htaccess file and yes, the W3TC code was generated before the wordpress code. I moved it, but I don’t know if this will necessarily be a fix or not as I haven’t had issue since last night so I can’t be sure what fixes the issue if it doesn’t occur again. We’ll see.