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

  • I started blogging one year ago, and I chose GoDaddy for my hosting (BIGGEST MISTAKE EVER) and now am suffering all the time with their really cheap hosting, errors, downtimes, and useless support !

    My wordpress based blog gets down several times a day, and I’m also suffering with the error “500 Internal server error” when I load my website, and I asked for their help numerous times but all I get was useless answers.

    I even tried to upgrade my account to their 4 grid hosting (supposedly better), yet non of issues were solved, if fact things have became even worse !

    I tried to google my frequent “500 internal sever error” problem just to find out that many out there are suffering the same problem with GoDaddy.

    I heard turning of the FastCGI may resolve the problem, but I don’t know how to do that, do any one have any idea ? This will be my last chance with GoDaddy then I’m moving to another webhosting company.

    The funny thing is that when I asked friends who are running similar blogs with other web hostings, they said their blogs were down maybe once or twice during a whole year, while my GoDaddy hosted blog gets down 10/20 times a day !!

    Thanks GoDaddy for ruining my life and my hardwork !

Viewing 15 replies - 61 through 75 (of 95 total)

  • Scanned for security issues with nothing wrong and I also checked the reliability and build of my database yesterday and optimized it, so nothing should be abnormal there…..website is back down again.

    I’ll be trying the last couple of things you mentioned.

    Hmm ok now i am seeing latency and timeout issues. yep now this could still not be a Server problem, but it sure looks like one.

    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Request timed out.
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=138ms TTL=44
    Request timed out.
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=149ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=213ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=138ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=151ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=128ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=81ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=95ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=95ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=167ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=198ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=193ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=169ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=86ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Request timed out.
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=138ms TTL=44
    Request timed out.
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=149ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=213ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=138ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=151ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=128ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=81ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=95ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=95ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=167ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=198ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=193ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=169ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=86ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=83ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=82ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=206ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=187ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=79ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=120ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=140ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=129ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=89ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=271ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=72ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=114ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=187ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=197ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=72ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=72ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=84ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=174ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=149ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=165ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=145ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=150ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=172ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=125ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=121ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=114ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=85ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=96ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=131ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=159ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=128ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=163ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=143ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=142ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=142ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=157ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=142ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=155ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=151ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=127ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=145ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=145ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=163ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=124ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=150ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=156ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=144ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=151ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=155ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=167ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=160ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=146ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=141ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=148ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=150ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=159ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=136ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=132ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=165ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=146ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=146ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=147ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=145ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=157ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=150ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=157ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=149ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=159ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=147ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=128ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=125ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=136ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=154ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=122ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=110ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=146ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=141ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=128ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=117ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=108ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=116ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=108ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=129ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=140ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=135ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=152ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=144ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=158ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=162ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=141ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=142ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=150ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=154ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=168ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=179ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=147ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=147ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=159ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=157ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=169ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=167ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44

    And this is a normal typical response. this segment of the ping is me visiting your site and you see a normal slight flucuation.

    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=105ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=110ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=92ms TTL=44

    I’m getting around this with each ping (give or take 1 or 2 ms)

    Reply from 184.168.37.1: bytes=32 time=80ms TTL=55

    tracert showed I was okay but site is down through browser.

    Just noticed I had a few timed out pings. Not consecutively, but randomly throughout

    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.

    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.

    @wampdog29,

    What version of PHP is your site being hosting with?

    5.2

    I am not sure about using 5.3 on Linux, but my host finally made 5.3 available to me (Running with IIS7), and the site is running much better now. I don’t know if at the same time they made any other modifications to how 5.3 is handled or run, but it did make a great bit of difference.

    5.3 should NOT be used on GD Linux hosting if you are using a custom php.ini file and want the Zend Optimizer to work. Additionally you MUST have this php handler in your root .htaccess file in order for your custom php.ini file and Zend Optimizer to work correctly.
    # GoDaddy 5.2.x PHP Handler
    AddHandler x-httpd-php5 .php

    and custom php.ini files are named php5.ini for GD. They are the only host that i know of that uses this naming convention for a custom php.ini file. ??

    tracert showed I was okay but site is down through browser.

    ahh this is good info! ping -t is better though because you are checking your site directly instead of checking all the hops along the way. any way if it was a Server problem then you would have seen a time out too.

    Yep i think caching could very well be either all or part of the puzzle.
    Another thing is that if your site shows a time out when someone visits it then something about your coding or DB or caching is causing that time out and probably not the Server itself. A more typical Server problem is no one is visiting your site and you are seeing time outs. ??

    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.

    I just ran ping -t and checked your site. bummer the problem still exists. and yep FastCGI and WP don’t play nice together. ?? Since you are using a custom php.ini file are you using the 5.2.x PHP handler in your root .htaccess file too? If you don’t add that handler than your custom php.ini file will not be used and the GD default php.ini will be used instead.

    Your custom php5.ini file should also have the Zend Optimizer directives in it.
    zend_optimizer.optimization_level=15
    zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.3.3
    zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3
    zend_extension=/usr/local/Zend/lib/Optimizer-3.3.3/ZendExtensionManager.so
    zend_extension_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3/ZendExtensionManager_TS.so

    Pinging greatgamingcrusade.com [184.168.37.1] with 32 bytes of data:

    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=71ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=146ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=115ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=85ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=118ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=177ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=139ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=181ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=210ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=167ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=149ms TTL=44
    Request timed out.
    Reply from 184.168.37.1: bytes=32 time=147ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=77ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=69ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=70ms TTL=44
    Reply from 184.168.37.1: bytes=32 time=72ms TTL=44

    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.

Viewing 15 replies - 61 through 75 (of 95 total)
  • The topic ‘Suffering with GoDaddy hosting downtime and"500 internal server error"’ is closed to new replies.