When a website reports a “Code 500 – Internal Server Error” to you, it’s more than annoying. In this case, as a visitor to the site, there is often not much you can do. GIGA explains to you what options you have to access the website after all.
Languages: German, English, French
As the error message “Code 500 – Internal Server Error” already indicates, this is a serious problem of the server that can have many causes. These are usually software problems on the website, such as interruptions in the database connection or simply errors in the configuration of the website. In rare cases it is sufficient if you load the website again.
Our video explains what you can do if you get a server error 500:
What can the website visitor do with an Internal Server Error 500?
The visitor to a website cannot change the cause of the error. He didn’t cause it. Sometimes just reloading the page is enough.
When it comes to pure content, it often helps to look at a saved version, for example on Google. All you have to do is precede the current website with a special Google call:
So for example
In the event of an internal server error, Google will at least display the content
Then Google will show you the last saved version of this website, which hopefully wasn’t an error message at the time. You can easily access images and text. However, the situation is completely different with the functions of the server. You can’t get forms or shop systems to work in this way. It usually helps to inform the website operator about this. He often doesn’t even notice it himself, because most servers do document their errors but don’t report them to the operator. If that doesn’t work, the only thing that helps is to wait.
Tips on the same topic:
Error reporting can also be fun, as you can see in these images:
What can the webmaster do with an Internal Server Error 500?
What’s mean about this server message is that it’s so unspecific. Theoretically, it could also say “Something’s going wrong here!”. There are nine other server error messages (501 – 510) that narrow down any problems. But usually you only get this collective message. If it then becomes more precise, then it is usually an error of the “502 Bad Gateway” variety.
As the operator of a website, you are at least initially forced to search and poke around when this Internal Server Error 500 occurs suddenly and unexpectedly. If you have just changed something, installed new plugins or tweaked your server configuration, then this is usually still understandable. Especially CMS systems like WordPress or Joomla offer the possibility to download helpful plugins. However, they are not always completely error-free and so they can influence each other, so that in the worst case there is a “500”. In such a situation, it usually helps to delete the plugin immediately.
The Internal Server Error 500 gives at least one hint here
It becomes more difficult when you have worked in the server’s configuration files. For example, tiny errors in the .htaccess file can lead to such errors. It’s enough to forget a hash, put a period in the wrong place or mix up a key and insert a semicolon instead of a colon. Would you like a small example? The line “deny from 107.20.” Doesn’t cause any problems. But a dot in the wrong place and “deny from .107.20.” results in a 500: Internal Server Error.
How do you use the internet? (Opinion poll)
Don’t want to miss any more news about technology, games and pop culture? No current tests and guides? Then follow us on Facebook (GIGA Tech, GIGA Games) or Twitter (GIGA Tech, GIGA Games).