In this article, you will learn:
Error 500: Internal Server Error
You can recognize Error 500 by the large Internal Server Error message at the top of the page. Under the heading, you will find a description of the error and a link to this article.
You may encounter Error 500 Internal Server Error on any website on the internet. It is a non-specific error returned by the server when it cannot describe its error state with a more specific 5XX code.
Solving Error 500
Error 500 is most often caused by:
.htaccess files
If Error 500 appears immediately after entering the website address, it is very likely a problem with the .htaccess file. You can find .htaccess files in the www folder, and they may also be in its subfolders. Any of them may be causing Error 500.
In all .htaccess files on the Webhosting (with the exception of functional alias domains and subdomains), check:
- Disallowed directives: .htaccess files installed by content management systems and their plugins may contain disallowed directives. Comment out lines with these directives by placing the # character at the beginning of the line. For example, you can comment out the disallowed code
Options -MultiViewsby changing it to#Options -MultiViews. - Errors in the code: If you are editing existing code, make sure you have not accidentally overwritten or deleted key parts.
Make edits to .htaccess files via FTP. Instructions can be found in the article Webhosting – File Management.
If you are using the default .htaccess file in the www folder with your own modifications, you can restore it according to the instructions in Webhosting – .htaccess File. During this restoration, the system will also create a backup of the .htaccess file in the www folder that you are replacing with the default one.
Duplicate subdomain directories
If you have one subdomain created both in the www/domains and www/subdom folders, Error 500 may occur. Choose one of these folders as the primary one and remove the other entirely. More information about subdomains on Webhosting can be found in the article Webhosting – Subdomains.
Webhosting limits
If Error 500 appears only after a longer loading time, your application may have hit one of the Webhosting limits ⧉: max_execution_time, memory_limit, post_max_size, or upload_max_filesize. You can optimize the application with these limits in mind, or switch to another service or its variant. More information about Webhosting and its alternatives can be found, for example, in the article Webhosting – Manual.
Frequently asked questions
I see Error 500 on the screen, but it looks different. What is happening?
Verify that the website is actually running on Webhosting/WMS, for example by using domain diagnostics. If so, contact support ⧉. If it is not our Webhosting (this also applies to our VPS), resolve the issue according to the instructions of the provider or server software.
Is Error 500 specific to VEDOS servers?
You may encounter error 500 on any web server. When solving this problem, use information about your content management system and the plugins used – a common source of the sudden occurrence of Error 500 is their automatic updates and rewriting of the .htaccess file.
How do I solve Error 500 specifically in the PrestaShop content management system?
The solution is described in the community article PrestaShop – error 500.