ause of HTTP 500 Errors
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Most of the time, "gone wrong" means an issue with the page or site's programming, nothing you have anything to do with.
Note: More specific information about the cause of a particular HTTP 500 error is often provided when it occurs on a server using Microsoft IIS software. Look for numbers after 500 as in HTTP Error 500.19 - Internal Server Error which means Configuration data is invalid.
How To Fix the 500 Internal Server Error
Like I alluded to above, the 500 Internal Server Error is a server-side error, meaning the problem probably isn't with your computer or Internet connection but instead is a problem with the web site's server.
While not probable, it is possible that there's something wrong on your end and we'll look at some things you can try.
Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar.
Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful.
Note: If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders - and multiple charges! Most merchants have automatic protections from these kinds of actions but it's still something to keep in mind.
Clear your browser's cache. If there's a problem with the cached version of the page you're viewing, it could be causing HTTP 500 issues.
Note: Internal Server Errors are not often caused by caching issues but I have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try so don't skip it.
Delete your browser's cookies. Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you're getting the error on.
After removing the cookie(s), restart the browser and try again.
Troubleshoot as a 504 Gateway Timeout error instead.
It's not very common, but some servers produce a 500 Internal Server Error when in reality the more appropriate message based on the cause of the problem is 504 Gateway Timeout.
Contact the website directly. Chances are good that the website administrators already know about the 500 error but if you suspect they don't, letting them know helps both you and them (and everyone else).
The best way to find contact information for a website is through a WHOIS search, using the domain name (e.g. facebook.com) as your search term.
If an email address isn't listed, try webmaster@website.com, replacing website.com with the actual website name. Sending a message to the site via their social networking profile is another good idea.
Come back later. The 500 Internal Server Error message is one of the most common HTTP error messages seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
Even if you're getting the 500 error on a site that doesn't sell anything, as long as you've let them know about the problem, there's little more you can do than wait it out.