We have all seen. As common as it is notorious, terrible HTTP500 internal server error will become an online store owner smile confused frown with one click. Lost sales omen, it stonewalls customers browse your store and purchasing power of the product. For Web developers, this error is a nightmare, creating a frenzied scurry to keep your store back online.
Although it sounds terrible, it’s not all scary. I will explain the error, and provides troubleshooting ideas for your Prestashop shop. You see this error, instead of hiding under your blanket next time you are ready to act quickly to solve the problem, and continues to sell.
How to identify errors 500
First, we need to go, you may see this error in different ways on your computer information. There are different forms of this message, because each host / server allows you to customize its display mode. Here is what you might see the way some common mistakes.
- “500 Internal Server Error”
- “HTTP 500 – Internal Server Error”
- “Internal Server Error”
- “HTTP 500 Internal Error”
- “500 Error”
- “HTTP Error 500″
Most of the time, you’ll see this message along with the various forms of this classic ambiguous line
“The server encountered an unexpected condition prevented from meeting the client requests it.”
Note that this error can be displayed on any browser and operating system (sorry, but switch to the new Mac Pro will not solve the problem), this is one of your browser this error approach may be displayed theme is very important.
500 What is wrong?
Simply put, it is the wrong way to say 500 Web server “accident, but I can not tell you, I’m sorry.” This is what we call “server” error. This means that there is something wrong web server who is sponsored. It is usually caused by a very common mistake with the website programming, PHP configuration issues or system privileges.
How can I fix?
Do not worry; though this is absurd vague error message, you still have a way to find more information. Web servers almost always configured to hide specific error messages. If your Prestashop store from debilitating pain errors, you can open Prestashop errors from the FTP or hosted cPanel report to get more details.
There are two ways to open up to you what version of Prestashop error report.
For PrestaShop v1.4 through v1.5.2
- Open config/config.inc.php
- On or around line 29 you will find this line
- Change that line to read
For PrestaShop v1.5.3+
- Open config/defines.inc.php
- On or around line 28 you will find this line
- Change that line to read
Once you enable error by FTP or cPanel report, you can return to your front or back office PrestaShop, reproduce the error or issue you have. For example, if you can not access because the 500 error site, you will need to open the error report, error and refresh the page. There will be additional information that you can use it to investigate the problem.
Once you have more information, there are some standard errors the way for further investigation. First, let’s look at some of the most commonly used method causes this problem. Once we find the cause of the error, it is very easy to solve.
In many cases, you will find that you allow in a folder is not set correctly. This may be a simple fix from 777-755, and vice versa swap file permissions / folder. In most cases, permission set 777 is very insecure, even an amateur can allow hackers to access your files and the malicious code inside. Be sure to check with your hosting provider to learn about setting up some servers have different rules specific information rights.
Incorrectly configured .htaccess:
Many times when htaccess file is not configured properly, you will receive an internal server error. For the purposes of PrestaShop, htaccess error is the main culprit, “URL rewriting” setting, or friendly URL enabled. htaccess syntax is very strict so even a bad character or command will cause the server or enable the option through the friendly URL or by switching back to the office to return an internal error 500 make your backup and rebuild htaccess htaccess file.
Each server has its own time-out setting that any given script can run. If the function or script through the limit, you will receive an error 500. Prestashop most common script, it can take too long to load the CSV import, backup, load transfer, import / export and thumbnail regeneration. Multiple server limit is 30 seconds, which is not long enough to run these scripts. You should contact your hosting provider and ask about changing the limit, at least temporarily.
Now, if the problem is not resolved to investigate these common causes, you should also look at the Apache and PHP error log. This is provided by your hosting provider, but sometimes you need to get them to directly contact these log files.
Put together puzzles
As cliche as it sounds, once your PrestaShop and / or error logs get an error message, (PrestaShop add words to your search and hone in on the issue) with Google, you’ll find plenty of information and search tutorials about your mistakes. No doubt, you will find some forums PrestaShop thread with them [solve] tag. Be sure to take the time to read this.
Does not solve the problem if you can not read this article, research on the internet and work / hosting provider and your webmaster, you must take to register and post time in the Prestashop forums. With more than 500,000 members of the community, we will ensure that the issue [solved]. You can send a message (username: “This Jiemingbaike”), and I link to your forum posts, I’ve certainly will take a look at our team of experts and the promotion of community managers and moderators answers.
I tell you 500 Internal Server Error is not so terrible as it seems. Now you have a good knowledge for navigation and resolve one of the most worried about the Internet wrong. Make your Prestashop online store, and to continue to sell!