The 500 error is a problem that can occur from time to time, particularly during the update of your website's theme or modules. This article presents the main causes and solutions to 500 errors.
|
💡 The article '500 Error after installing or updating a module' details this specific case. |
Permission error
In many cases, you will find that the permissions of the folders are not set correctly.
To correct this error, you simply need to set the permission of a file or folder to 755 instead of 777 (or vice versa).
As a general rule, permissions of 777 are incredibly poorly protected and even an amateur hacker can access your files and introduce malware.
Consider the hosting: check the specific characteristics of the permissions with your host, as some web servers use different rules.
Incorrect configuration of the .htaccess file.
Internal server issues are often caused by a misconfigured .htaccess file.
Regarding PrestaShop, the issues are generally related to URL rewriting options and the activation of "friendly URLs."
The syntax of a .htaccess file is very strict, and even a single incorrect character or command could cause an internal server error 500. Therefore, since the 'friendly URLs' option is available, indicating 'NO' could be a solution (do not forget to save your changes).
We recommend that you back up your .htaccess file and restore it from the back office or disable 'friendly URLs'.
Time out.
Each web server has its own timeout, which determines the execution duration of a script. If the function or script exceeds this time limit, you will receive a 500 error.
Here are the PrestaShop scripts that may take too long to load:
- Importing CSV files.
- Backup files.
- Loading translations.
- Imports/exports.
- Regeneration of thumbnails.
Often, the server's time limit is 30 seconds, which is insufficient for these scripts.
In this case, you should contact your hosting provider and ask them to modify this setting (at least temporarily).
In the case of importing CSV files, error 500 can sometimes be due to exceeding the maximum execution time, and not all hosting services allow modifying this setting.
Obsolete modules.
It is possible that when you update your store, for example if you upgrade from version 1.7 to version 8, you may encounter outdated or incompatible modules with this new version of PrestaShop.
This may generate errors 500. In this case, you should review all the addons you have installed, or at least those that are available in a more recent version.
We recommend that you always have on hand (or saved in your favorites) the official page of the PrestaShop Marketplace, where you can obtain recent modules.
5. Incompatible modules, themes, or extensions
Whether you are using PrestaShop or another CMS (WordPress, Shopify), installing plugins, themes, or extensions on unsuitable content management systems can trigger conflicts and create an internal server error.
If the 500 error was triggered following the installation of new modules, please refer to the article "500 Error after Installing or Updating a Module" for guidance.
What should I do if the 500 error persists on my site or web page after these checks?
If these solutions do not resolve the issue, we offer Advanced Technical Support which includes a comprehensive diagnosis and a personalized resolution of your problem. For any questions or to proceed with this option, please do not hesitate to contact us.