WordPress.org

Support

Support » Multisite » Error 500 on http header

Error 500 on http header

  • I’m running WordPress in multisite mode with several subdomains. Everything is as it should but for one single subdomain.

    There I keep getting an error 500 on the http header. The site itself is rendered normally, but search engine like Google and other non-human users don’t see anything.

    This is the header:

    HTTP/1.0 500 Internal Server Error =>
    Date => Tue, 17 Jan 2012 19:30:44 GMT
    Server => Apache
    X-Powered-By => W3 Total Cache/0.9.2.4
    Expires => Tue, 17 Jan 2012 19:32:15 GMT
    Last-Modified => Tue, 17 Jan 2012 19:30:45 GMT
    Cache-Control => max-age=90, public, must-revalidate, proxy-revalidate
    Pragma => public
    X-Pingback => http://walburgisgymnasium.smmp.de/xmlrpc.php
    Vary => Cookie,Accept-Encoding,User-Agent
    Connection => close
    Content-Type => text/html; charset=UTF-8

    My provider (the site is on a dedicated server) says, there is nothing in the error logs and the error must be coming from a script.

    They were as nice as to have a look at the scripts in my webspace and found these rather suspicious:

    /wp-content/plugins/nextgen-gallery/admin/ajax.php: header(‘HTTP/1.1 500 Internal Server Error’);
    /wp-content/plugins/nextgen-gallery/admin/ajax.php: header(‘HTTP/1.1 500 Internal Server Error’);

    /wp-app.php: status_header(‘500’);
    /wp-includes/functions.php: status_header( 500 );

    I already dealt with NextGenGallery by deleting it completely from the server (funny enough, Highslide4WP is still announcing a conflict with NGG), but the error 500 is still there. I also deactivated the five other plugins running on that faulty site, but that didn’t change anything either.

    My provider’s idea was a thorough debugging job on the scripts mentioned above. Unfortunately, that isn’t an option for me since I wouldn’t dare to touch those WP core file even if I had some foggy idea about debugging.

    This error keeps the site from getting listed in search engines which is an absolute must and at least as urgent as food and drink.

    So, any ideas that would rid me of that error are highly appreciated.

Viewing 10 replies - 1 through 10 (of 10 total)
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error 500 on http header’ is closed to new replies.
Skip to toolbar