The HTTP error 500 is a generic HTTP status code which occurs when the web server encounters an unexpected condition
that prevents it from returning the requested webpage. The web server is unable to be more specific about the cause of the error.
Also known as an Internal Server Error, the HTTP 500 error will be reported
by your browser but the problem is with the website itself.
When the HTTP error 500 occurs, the web server will generate an internal error log which will provide details of what caused the problem.
Using these logs, the operators of the web server should be able to analyse the cause of the HTTP error 500 and fix it.
The HTTP 500 error occurs on the web server and therefore this can only be resolved by fixes to it. It is not a web browser problem.
It is up to the operators of the web server to locate and analyse the logs which give information about the cause of the error 500.
In some cases the cause of the HTTP 500 error can be cached versions of the website's code on the browser causing the unexpected
condition on the web server. For this reason it is worth clearing the cached files within the web browser for the site reporting error 500.
If you're the owner of the website, the first thing you should do when you encounter an HTTP error 500 is check the web server logs.
For example in the Apache 2 web server a typical location would be in /var/log/apache2.
Typically the file will be called error.log but might be different if the web server has been configured with a different format.
For Internet Information Services (IIS) the default location for the log files are in %SystemDrive%\inetpub\logs\LogFiles
Our service monitors your site for HTTP errors such as 500. Please contact us (email preferred) whenever you encounter a HTTP 500 error on your CheckUpDown account. We can the liaise with your ISP and the vendor of the web server software so they can trace the exact reason for the 500 error and help resolve it.
Microsoft's Internet Information Services (IIS) web server has more detailed error 500 messages:
For more on IIS specific status codes see The HTTP status code in IIS 7.0, IIS 7.5, and IIS 8.0
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
HTTP error 500 occurs in the final step above when the client receives an HTTP status code that it recognises as "500".
The Web server thinks that the HTTP data stream sent by the web browser was correct, but access to the resource identified by the URL is forbidden.
The Web server (running the Web site) thinks that the HTTP data stream sent by your web browser was correct, but simply can not provide the access to the resource specified by your URL.