PrestaPrestaShop 500 Error: The Checklist to Get Your Store Back Online in Under an Hour
A blank page or 500 error can cost you several hundred euros per hour. Here is the exact process we follow for emergency troubleshooting.
Every Hour of Downtime Costs You Money
A PrestaShop store generating €3,000 in daily revenue loses around €125 for every hour it is down. The priority is not to understand the issue—it is to get the store back online first, then investigate the cause.
1. Enable Debug Mode (2 Minutes)
In config/defines.inc.php, set _PS_MODE_DEV_ to true while you troubleshoot. The 500 error will be replaced by a specific message: missing class, insufficient memory, or SQL error.
2. Check the Actual Logs
Check these three locations, in this order:
var/logs/(PrestaShop 1.7 / 8)- your hosting provider's PHP error log
error_login the site's root directory
3. The Five Most Common Causes We See
- A newly installed module breaking a hook.
- A conflicting override after an update.
- A
memory_limitthat is too low for a catalogue import. - A corrupted Smarty cache: clear
var/cache/. - A PHP migration (8.1 → 8.2) running outdated code.
4. Restore a Stable Version
Disable the faulty module directly in the database (ps_module, active column), clear the cache, and test the store. This gets your store back online—the permanent fix comes next.
Need Help Right Now?
We provide PrestaShop emergency support from 9:00 am to 10:00 pm, 7 days a week, with a response within 1 hour and a free diagnosis before any work begins.