Title: Error 500 on http header
Last modified: August 20, 2016

---

# Error 500 on http header

 *  [Andreas](https://wordpress.org/support/users/sauerland/)
 * (@sauerland)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/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](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)

 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [14 years, 4 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513084)
 * Did you flush the cache for w3TC on that site?
 *  Thread Starter [Andreas](https://wordpress.org/support/users/sauerland/)
 * (@sauerland)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513092)
 * I flushed the cache every time I tried something new and even deactivated w3tc
   completely. Didn’t change anything.
 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [14 years, 4 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513177)
 * Well the usual tricks are to turn off all your plugins and see it works.
 *  [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513456)
 * Removing the .htaccess directives for page cache resolves the issue?
 *  Thread Starter [Andreas](https://wordpress.org/support/users/sauerland/)
 * (@sauerland)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513457)
 * 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.
 *  [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513458)
 * Any chance you have specific steps to duplicate?
 *  Thread Starter [Andreas](https://wordpress.org/support/users/sauerland/)
 * (@sauerland)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513461)
 * 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).
 *  [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513472)
 * So you’re using object caching?
 *  Thread Starter [Andreas](https://wordpress.org/support/users/sauerland/)
 * (@sauerland)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513473)
 * Yes, with APC.
 *  [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [13 years, 10 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513536)
 * 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.

## Tags

 * ["internal server error"](https://wordpress.org/support/topic-tag/internal-server-error/)
 * [ajax.php](https://wordpress.org/support/topic-tag/ajax-php/)
 * [debugging](https://wordpress.org/support/topic-tag/debugging/)
 * [error 500](https://wordpress.org/support/topic-tag/error-500/)
 * [multisite](https://wordpress.org/support/topic-tag/multisite/)
 * [next-gen gallery](https://wordpress.org/support/topic-tag/next-gen-gallery/)
 * [subdomain](https://wordpress.org/support/topic-tag/subdomain/)
 * [wp-includes/functions.php](https://wordpress.org/support/topic-tag/wp-includesfunctions-php/)

 * In: [Networking WordPress](https://wordpress.org/support/forum/multisite/)
 * 10 replies
 * 3 participants
 * Last reply from: [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * Last activity: [13 years, 10 months ago](https://wordpress.org/support/topic/error-500-on-http-header/#post-2513536)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
