Code 500: Internal Server Error Google Chrome | How to Fix? | What is it?


If a website reports a “Code 500 – Internal Server Error”, this is more than annoying. In this case you can’t do much as a visitor of the site. Tugberk.net explain to you which possibilities you have to access the website after all.

As the error message “Code 500 – Internal Server Error” already indicates, this is a serious server problem that can have many causes. These are mostly software problems of the website, such as database connection interruptions or simply errors in the configuration of the website. In rare cases it is sufficient to reload the website.

What can the website visitor do in case of an Internal Server Error 500?

The visitor of a website cannot change the cause of the error. He has not caused it. Sometimes it is enough to simply reload the page again.

When it comes to pure content, it often helps to look at a saved version, e.g. at Google. To do this, you just have to prefix the current web page with a special Google call:

http://google.com/search?q=cache:
So for example
http://google.com/search?q=cache:tugberk.net

Then Google will show you the last saved version of this web page, which hopefully was not an error message at that time. Pictures and text can be accessed without any problems. But it looks completely different with server functions. Forms or shop systems will not work this way at all. It usually helps to inform the website operator about this. Often he doesn’t even notice it himself, because most servers document their errors well-behaved, but don’t report them to the operator. If that doesn’t work, all that helps is to wait.

What can the webmaster do in case of an Internal Server Error 500?
What’s wrong with this server message is that it is so unspecific. It could theoretically say “Something is going wrong!” There are nine more server error messages (501 – 510), which narrow down possible problems more precisely. But mostly you only get this collective message. If it gets more precise, then it is mostly an error of the type “502 Bad Gateway”.

As the operator of a website, you are forced to search and search for it at least once, if this Internal Server Error 500 suddenly and unexpectedly occurs. If you have just changed something, installed new plugins or changed your server configuration, this is usually still understandable. Especially CMS systems like WordPress or Joomla offer the possibility to reload helpful plugins. But they are not always completely error-free and so they can influence each other, so that in the worst case it comes to a “500”. In such a situation it usually helps to delete the plugin immediately.

It becomes more difficult if you have worked in the configuration files of the server. For example, tiny errors in the .htaccess file can cause such errors. It is enough to forget a hash, put a dot in the wrong place or mix up a key and insert a semicolon instead of the colon. Want a small example? The line “deny from 107.20.” does not cause any problems. But a dot in the wrong place and “deny from .107.20.” causes an error 500: Internal Server Error.