Przejdź do głównej zawartości
Wersja: 6.4.0

Apache 500 - Internal Server Error

It is a common scenario for people responsible for installation, updates, and implementation of the system to receive error 500 in the browser. The first thing to understand is that this type of error isn’t an application error, but an http server error. However, it doesn't mean the application itself cannot cause the problem, but it means that the http server knows why this error appeared. Therefore, the most important information is why the http server displays the error. Read the following information to learn more about the error:

Enable http server logs and determine what causes the error​

  • If you can’t see anything relevant in the logs - you will have to enable more detailed http server logs. Error 500 is a server error, and therefore the server knows best why the error is displayed.
  • If you don’t know how to enable logs - you should ask your server administrator to do it for you, or contact the server provider support.
  • YetiForce application logs may include a hint why the problem occurs, but you should mostly focus on what the server logs show.

The most common causes of error 500​

  • temporarily exceeding security services parameters, including the scripts run by www. You can try to undo the last changes performed in www service, disable scripts/applications that can significantly burden the server.
  • exceeding the timeout parameter for the server. You can solve the problem by modifying scripts, so that their execution time doesn’t exceed the service safety parameters.
  • misconfigured file and directory permissions. You can change CHMOD, for example while connecting to the FTP server.
  • incorrect entries in the .htaccess file. You can solve the problem by removing or fixing incorrect directives, for example syntax errors, or calling options unavailable on the server.

How can the YetiForce team help you to solve this problem?​

This error is server-specific and requires an analysis of server logs, therefore the YetiForce team can only help you solve this problem directly if you purchase support hours available in our store.

How can the community help you solve this problem?​

If you submit a ticket in the Issue tab of our GitHub repository, you can try to solve the problem together with the community. Remember to include the http server logs, because if you don’t provide them, identifying the problem will be hardly possible.

If you find an error message and you have no clue what to do with it, you should ask the operating system administrator to conduct an analysis, or research the problem on the Internet on your own. Our team can only offer advice as far as configuration and development of the YetiForce system is concerned. When it comes to assistance with server issues, we recommend contacting companies who specialize in this area. We have Linux server specialists, but they support us in the development of the product, and they also help us during the implementation of paid projects.