Support » Networking WordPress » 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/
    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 =>
    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)
  • Did you flush the cache for w3TC on that site?

    I flushed the cache every time I tried something new and even deactivated w3tc completely. Didn’t change anything.

    Well the usual tricks are to turn off all your plugins and see it works.

    Removing the .htaccess directives for page cache resolves the issue?

    I don’t know. Got it running again after killing NextGen Gallery multisite-wide. The error disappeard and didn’t come back when I reinstalled the gallery plugin. Very obscure.

    Any chance you have specific steps to duplicate?

    If something like this occurs I usually try so many things in fast sequence that I finally don’t know what did the trick. There is one thing, though, that really troubles me in these erratic fault finding fits: The backend is being cached – no matter what the plugin claims not to do. On a multisite a newly installed or deactivated plugin only shows when I flush the cache on the network AND on the individual site. Same goes with changes taking effect. Some things fall into perfect harmony a day later (provided I bit the dust in the meantime and didn’t go on with my untutored fiddlings).

    So you’re using object caching?

    Yes, with APC.

    Frederick Townes


    That’s likely the issue. Improved compatibility is amount the goals in the forthcoming release.

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