500 Internal server error – premature end of headers – Can’t access site

  • Hi. I have a blog at https://www.fastandbad.com. I currently have a HTTP 500 Internal server error. According to the log files, I have this problem:
    Premature end of script headers: index.php
    When I contacted Dreamhost, they told me about this error, and that I seem to be using the maximum allocated amoun of RAM.
    I have a very simple blog with a few plugins.
    Last week I allowed a “pingback” froma website that linked to, of all things, a cookie recipe I had posted.
    I would go into WordPress and disable my plugins or the pingback, but because of the internal server error, I can’t even get to the Admin screen.
    If anyone has any tips on how to fix this, I’d appreciate it. I have not changed anything recently besides that pingback.
    Thanks for youur help.

Viewing 3 replies - 1 through 3 (of 3 total)

  • Just ask them to update your RAM or move onto a new server

    Thread Starter izumino

    (@izumino)

    Hi. I appreciate your feedback, but since the Blog was fine before the pingback, and now has the internal server error, and I have made no changes that would need an increase in RAM, I’m hoping to find a solution (such as disbaling plugins, though I can’t reach through a web interface) as to how I can re-access the site from the existing configuration. Thanks.

    I have the same problem. I use Dreamhost and WordPress on my blog, and here’s what Dreamhost reply me:

    It looks like the issue is that one of your php scripts is using too much
    resources for shared hosting. This is causing our procwatch daemon to
    notice that usage and kill your process to help keep the server in line.
    I would usually recommend looking into your code to see if you can
    optimize it’s memory/cpu usage. However, it looks like you are using
    WordPress. As such, there’s a good chance this might have to do with a
    plugin you are using. I would recommend disabling your plugins (by
    renaming the plugins folder to something like “plugins.old”). If your
    site begins working at this point, this means that the issue was with a
    plugin. As such, you should recreate the “plugins” directory and slowly
    begin re-adding the plugins one-by-one and testing it after adding each.
    If it breaks after one of them, than this is likely the cause.

    If this doesn’t help, chances are your blog has outgrown shared hosting.
    In this case, I would recommend looking into our Dreamhost PS service:

    https://dreamhostps.com

    Izumino, how did you solve your problem?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘500 Internal server error – premature end of headers – Can’t access site’ is closed to new replies.