Joomla! HTTP 500.0 error

Joomla! HTTP 500.0 error

Fix Joomla HTTP 500.0 error after Joomla! update to version 3.2

Over the last week we, at Vevida, received quite a lot problem reports by customers who updated Joomla! to Joomla! version 3.2.0. After logging on to their administrator back-end, they received an HTTP 500.0 error. Unfortunately this HTTP 500.0 has nothing important to tell, except Internal Server Error, The data is invalid. (0x8007000d). So, nothing much. This basically means that somewhere the output breaks fastCgi and PHP output.

Let’s investigate and resolve this Joomla! Administrator log in HTTP 500 error.

Joomla! HTTP 500.0 error

The Joomla administrator login HTTP 500.0 error looks like:

An IIS Failed Request Tracing report looks like:

Here’s how to fix this HTTP 500.0 (The data is invalid. (0x8007000d)) error after a Joomla! update, for example to version 3.2.0:



How to fix Joomla! administrator HTTP 500.0 after updating Joomla! 3.2.0

Luckily the error is quite easy to fix. If only I knew this earlier, it would have saved me some time :).

  1. when you’ve tried to log on and the HTTP 500.0 error is displayed, add ?option=com_installer&view=database in the address bar of your browser to the URI. The full URI then becomes
  2. after pressing the ENTER key on your keyboard, you’re automatically logged on to your Joomla! 3.2.0 administrator back-end.
  3. You’ll probably notice database errors. These database errors can be repaired in the back-end using the Fix-button, and this resolves the log in issue permanently





Joomla 3.2.4

This fix for HTTP 500 error on Joomla administrator login, after updating, is still valid for Joomla 3.2.4 update.



Sysadmins of the North
About The Author
My name is Jan Reilink. I am not a hacker, coder, developer, programmer or guru. I am merely a system administrator, doing his daily thing at Vevida Services in the Netherlands. With over 10 years of experience, my specialties include Windows Server (2003, 2008 and 2012), Windows 7, IIS (6.0, 7.5 and 8.0), Linux (CentOS, Debian), PHP, websites, optimization and security. More about me @



  • Mark Keus

    Thanks! Worked for me!

  • Valentin

    Thank you. it works for me. You are great.

  • Tim

    Yep, fixed my issue too, thanks!!

  • Sven

    THANK you so much You made my day try to fix this shit since yesterday xD

  • Paul

    Doesn’t help unfortunately. The login dialogue box still appears and the HTTP 500 error then aoccurs.

    • Jan Reilink

      Hi Paul,
      Thank you for your comment. I’ve tested this with an update to Joomla 3.2.4 and this still works.

About Sysadmins of the North

Hi and welcome to Sysadmins of the North!
Sysadmins of the North is just another technical blog. Just like so many others out there. Most posts are written in English, some in Dutch. On you can find all kinds of computer, server, web, sysadmin, database and security related stuff.

About me: My name is Jan Reilink. I am not a hacker, coder, developer, programmer or guru. I am merely a system administrator, doing his daily thing at Vevida Services in the Netherlands. Living in the north of the Netherlands, so hence the name Sysadmins of the North :-)
Drop me a comment somewhere or send an email to say hi, or discuss about security, website or WordPress, performance, Windows or IIS topics.


If you feel that Sysadmins of the North has helped solve your problem, saved you time, or you just simply like, then please consider making a donation with Paypal. Thanks! :)

Search & find

Custom Search
IT Books & WP Themes

Windows PowerShell Cookbook: The Complete Guide to Scripting Microsoft\'s Command Shell
DNS and BIND - 5th Edition
DNSSEC Mastery: Securing the Domain Name System with BIND
Windows Server 2012 Unleashed
Enfold - Responsive Multi-Purpose WordPress Theme
Striking MultiFlex & Ecommerce Responsive WordPress Theme


The Sysadmins of the North network

Just for the fun of it, Sysadmins of the North is hosted on mulitple servers:

  1. one (shared) Windows Server 2012, IIS 8.0 webserver running PHP 5.5
  2. one (shared) MySQL database server, running MariaDB 5.5
  3. one Varnish Cache HTTP reverse proxy with Nginx Droplet, for offloaded static content, running Debian 7.0 @ DigitalOcean
Easy share

Share this post easy on:
RSS feed
If you like
donate to Sysadmins of the North
Twitter Feed

What's happening, right now, around

Bad Authentication data
Copyright © 2007-2014 . Design by OrangeIdea