Status Code 500 – Causes & Solutions for Website Error – webgo blog

Post from November 28, 2019

If the status code 500 is output instead of the website called up, this is always a server-side error. In today’s post, we’ll show you what exactly the 500 error means, how to find the cause and, accordingly, a solution to fix the error.

500 Error as collective code for server errors

The 5 in the first position of this error code makes a statement about the error category. Accordingly, the status code 500 belongs to the Internal Server Error category. At first glance, you can’t see much more from this status. The only thing that is certain is that there are problems connecting to the server and therefore the page cannot be displayed as desired.

How to find out the cause of the 500 status code error?

The causes of the 500 error can be very diverse. It is often due to an error in the configuration of the web server. These include, for example:

  • corrupt .htaccess file

  • bad script

  • not enough memory to process the request correctly

  • incorrectly set permissions to run a file

In addition, the status code can also be due to an error during installation in the CMS, eg due to an incompatible plugin.

Tips to fix the 500 status code error

If the error affects you from the user’s point of view, you can do relatively little about it. But you can try the following to rule out all sources of error on your part or through your browser:

Clear your browser’s cache and then reload the website.

The error still occurs? Then you should wait a few hours before trying again. If you then see the 500 status code again, the only thing that can help you is to contact the website administrator.

Of course, if it’s your own site, your options for finding and fixing the error look better. You should also take care of it as soon as possible so that visitors and search engine bots can get back to you as expected.

The best way to do this is as follows:

  1. Did you make any changes to the template or the .htaccess file before the error? Then you first try to fix errors by undoing these changes.
  2. Check the server log data (error logs) – here you can see directly in which file the error occurs or what the specific cause of the incorrect response is.
  3. Checks if the server is still running. If not, then contact our support or your hoster.
  4. Checks the permissions of important files, i.e. the permissions for read (r), write (w) and execute (x) for the three user types file owner, group of users and others.

Further status code contribution: 404 error – meaning and tips for individual 404 pages.