wampdog29
Forum Replies Created
-
Well, I am running the default theme with no plugins and I got the error…..
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.
No help from GoDaddy by phone… wow
Forum: Fixing WordPress
In reply to: Backend Errors:: Premature end of script headersanyone ever find out what was wrong with your errors? I seem to be having this same issue.
I’ve tried just about everything: plugins deactivated, removed, theme change, lowering memory usage, switching from FastCGI, pinging, tracert.
I use GoDaddy and am pretty good with code, especially PHP. I receive the Premature end of script headers which either leads to the page displaying 500 internal server error, a page saying I don’t have permissions, logging me out or a simple cannot load page.
Mostly the 500 internal server error though and always a premature end of script headers index.php in my error log along with a timeout 120 seconds log.
Thanks for helping AITpro
This is definitely NOT resolved yet.
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.
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?
Site is inaccessible once again….
Yep. I was actually just thinking about doing that. I’ll get on that right now.
Yes, I have the GoDaddy php handler directives. Never knew about the Zend Optimizer directives though. Added those, but this site has been running fine for months without any of these changes or anything I’ve done within the last week to try and fix this issue.
My error logs ARE showing the damn premature end of script headers still along with the timeout of 120 seconds error. However, I have been editing and posting articles without a hitch along with browsing every section of the site non stop to try and get the onscreen server errors, but nothing so far.
I’m still getting the same exact ping info with the occasional timeout. From what I’ve read, getting a timeout every now and then while pinging isn’t necessarily something bad. If the ping time is about the same, then there shouldn’t be an issue. However, you ARE seeing spikes in ping time, while I’m not.
So, still, no clue. I’m betting around 11 PM EST to 3 AM EST tomorrow morning that I’ll start getting the errors again. I’m really betting it’s GoDaddy now. If it’s a database issue, plugin, theme or anything I have changed, I don’t think I could go 18 hours straight with no error and then all of a sudden get them again. No clue.
Yeah, I know all about the whole GoDaddy php5.ini issue. When I first started using them I was always feeling like I was running php v4 even though it said 5. Researched the whole custom php5.ini issue and changed the filename over and voila, it worked very well.
Haven’t had an issue since changing the caching issue, but we’ll wait and see. Unfortunately, I feel as though I don’t know exactly what still may have been the problem. For all I know, GoDaddy could have been messing around too and I also changed the FastCGI because I keep reading that I should not be using FastCGI…. so maybe that helped. Who knows.
5.2
Anyone know of W3 Total Cache causing these issues? Deactivated it and reactivated it yesterday and then checked in the settings. For some reason, the Database Caching was turned off and the Object Caching turned on. I always had that reversed because I used to have some minor issues with Object Caching.
Don’t know how they got reversed, but I changed them around and everything is fine again. I made sure to do this in the middle of getting the errors early this morning. Now, I’ll just wait a day and see if the errors come up ever again…. very odd.
Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] 500 Internal Server ErrorI believe I have come across this as well, although I may need another day to see if it really WAS the W3 Total Cache plugin. I have been receiving 500 internal server errors with my error logs showing “premature end script headers . index” or whatever.
So, I thought I got rid of the errors by deactivating Cubepoints plugins and aaaall day long I was fine until about 1 AM EST. Tried deactivating W3 Total Cache and so far, the site has been running fine. We’ll see….
Site is now back up again… strange.
Also, is it unusual to NOT see this fluctuation? Accessing my site is not showing any flux in my ping time.