X-Cart:500 Internal server error
Internal server errors can be usually caused by one of the following issues:
This is the most common cause of internal server errors. Please check your script documentation to ensure that you are using the correct permission levels. Permission levels can be changed using the chmod command (see http://www.manpagez.com/man/1/chmod/).
For example permissions for PHP and HTML files, images, and other files needing to be accessed from the web should be set to 644. All folder permissions should be set to 755.
If this still fails to resolve the issue, please contact our support team for advice.
- Setting up file permissions in X-Cart
- How to manage file permissions on UNIX server?
- How to configure access file permissions on Windows Server?
If the error occurs when submitting a form, chances are pretty good that the problem is mod_security.
To prevent this, we suggest turning off mod_security for the form you have troubles with. You can do so by putting an .htaccess file (or edit it if it already exists) in the folder where the form file is located, containing the following line:
For security reasons some hosting providers do not use mod_php on their servers. That means that "php_flag" or "php_*" directives cannot be placed into an .htaccess file on such servers, otherwise your site will generate "Internal server error".
Instead you can change these settings in php.ini file for your hosting space.
Wrong permissions on php and php.ini files
Removing or changing permissions for these files may cause an internal server (or other) error. Please make sure that those files exist and their permissions are correct (php file should have 555 permissions, php.ini file should have 644 permissions) or consult your hosting provider support team.
A 500 error may occur because a script is taking too long to execute. If the script is consuming a lot of the CPU load, the server will terminate it, thus resulting in an internal server error.
In this case hitting Refresh usually helps to reload the page. However, if you receive a 500 error often, you should consult the developer of the script.
If these fixes do not address or resolve the error you are experiencing or you require more clarification, please do not hesitate to contact our support team for advice.