Apr
04If you have visited this blog yesterday, you might see an 500 Internal Server Error instead. Yesterday when I was back from school, I switched my computer on, wanting to check my AdSense stats out and discovered I have less than half impression than what I usually have. I then check my blog and SiteMeter out and found that it’s having 500 Internal Server Error and was down for quite a long time.
Later, I work with people from DreamHost(aff) - disable all plugins one by one, renaming the plugin directory, renaming this and that, still not working. The techie from DreamHost have already no clue and send my case over the Level 2 support. No response until the time I go to bed. Today when I’m back, I immediately check if this blog is back, and thanks god - it’s back.
I have to re-activate those plugins one by one to make sure the blog work as usual. Later, check my mail saw DreamHost’s email saying that it has been resolved. The problem was caused by a file related to the wp-cache plugin.
Sorry for all inconvenience, especially those who try to visit but failed yesterday.
Some relevant posts you might be interested:
Was the problem specifically with the wp-cache plugin? I use that too so I’m naturally curious. Anyway, good to have you back.
[Reply]
luckily you know it earlier, if not, will affect ur earning o..haha
[Reply]
@Brown Baron: Well, I’m not really sure. But it should be safe since many blogs used it - it might be just my problem.
@maria: It’s already affected.
[Reply]
Was a specific component of wp-cache identified as the culprit? How was the determination made? I’m very curious as I’ve just moved over to Wordpress this weekend and have heard a lot about the advantages of using wp-cache.
[Reply]
I’m not really sure about it, maybe it was mistakenly thought to be wp-cache’s fault - or I installed other plugins that isn’t compatible with wp-cache.
[Reply]