PrestaShop down: 500 error, blank page, back office won't open - init.d - Linux systems, DevOps and PrestaShop development

PrestaShop down: 500 error, blank page, back office won't open

Your PrestaShop store isn't responding? We find the cause and get orders flowing again.

A PrestaShop store down with a 500 error, a blank page or a back office that won't open: we put it back online. The job starts from €149, with the price set in the quote before we start, and covers diagnosis from the logs, fix of a single cause (module, override, cache, PHP version, database or permissions) and a report explaining what happened and how to avoid it next time. A store that's down is a P1 emergency: during office hours we pick it up within one hour; out of hours within one hour with an on-call plan, otherwise within 24 hours if we already work together. It's done by sysadmins who write PrestaShop modules and run the servers it lives on.

Why does PrestaShop show a 500 error or a blank page?

A PrestaShop store that suddenly stops almost always has a precise cause, usually one of these:

  • a module just installed or updated that isn't compatible with your PrestaShop or PHP version;
  • leftover overrides in the override folder after a module was uninstalled, replacing core classes that have since changed;
  • stale cache: after an update or a file move, var/cache points to classes and templates that no longer exist;
  • PHP changed by the host: an automatic switch to a new version breaks an old store, or an old one blocks an updated store;
  • database: damaged tables, full disk, connection limits reached at peak traffic;
  • file permissions changed by a migration or a manual intervention.

Two of these causes deserve a note. Modules stuck on old versions are the most common reason for an outage after an update: how to spot them is explained in our article on PrestaShop modules stuck on version 8. And the PHP switch decided by the host often comes without notice, because the old version is out of support: the store that worked the day before shows a blank page the day after.

What you can safely check yourself

Before calling us you can do two checks that break nothing: ask your host whether anything changed (PHP version, limits, server migration) and recall the last change made before the outage, such as a module installed or an update launched. If you have file access, the host's error log often already says which file and line caused the error. Avoid deleting folders at random or reinstalling modules until the cause is clear.

What we do

  • Diagnosis from the logs: we enable debug mode in a controlled way and read the PHP and web server logs to find the component that fails.
  • Fixing the cause: we disable or fix the module, clean overrides and cache, realign the PHP version or permissions.
  • Store check: home, categories, product page, cart and checkout, plus back office access.
  • Quick malware check: if the outage is a symptom of an infection we stop and move to PrestaShop malware removal.
  • Report: what broke, what we changed and how to avoid repeating the mistake.

Price and terms

The starting figure covers diagnosis and fix of one cause on one store, during office hours: Monday-Friday, 09:00-18:00. We agree the price in the quote, free of charge, before we start: you approve it and only then do we touch the store. The other fixes are on the PrestaShop page.

Development - for example a custom module to fix - and work on the server are not included: if they're needed, we stop and update the quote before going ahead, hourly or with hour packages. A store that is down is a P1: during office hours we pick it up within one hour, with no extra charge. Out of hours the on-call rules apply: with a plan within one hour at the office rate, without one within 24 hours at the out-of-hours rate set out in the terms.

A typical case

A clothing store goes blank on Monday morning. On Friday a shipping module had been updated. The logs show an error in a cart override left behind by an old discount module, uninstalled months earlier: the new shipping module called a method the override no longer had. With the orphan override removed and the cache rebuilt, the store is back online in under an hour; the report also lists the two other leftover overrides, to remove at leisure.

Who it's for

  • PrestaShop stores down with a 500 error, a blank page, an inaccessible back office or a checkout that won't complete orders.
  • Shops that ran an update of core, a module or PHP and ended up with the store down.
  • Agencies and web studios looking after a client's design and content that need someone for the technical side.
  • Stores that changed hosting or server and won't start after the migration.

How we work

Write to us with the store address, the message you see and the last change you remember; we need access to hosting and back office. We read the logs, find the cause and fix it, then check home, categories, product page, cart and checkout before telling you everything is fine. The quote you approve covers the cause we find; if more causes emerge or development is needed, we stop and update it before going ahead. At the end you receive a report with what broke and how to avoid it, written to be understood by non-technical people too.

After the fix

If the outage came from an update run straight in production, next time it's better done on a copy: that's how we work in the upgrade to PrestaShop 9. To look after the store over time there is PrestaShop support with monthly maintenance, and for a full snapshot of the store's condition there's the store check-up.

Frequently asked questions

Why does PrestaShop show a blank page or a 500 error?

Almost always it's a fatal PHP error that PrestaShop doesn't display: a module just installed or updated, an override left behind by an uninstalled module, a cache pointing to files that no longer exist, or a PHP version changed by the host and not compatible with the store. The cause is read in the logs, not guessed.

Can I enable debug mode myself?

Yes: in PrestaShop 1.7, 8 and 9 you enable it from the back office (Advanced parameters, Performance) or, if the back office won't open, in config/defines.inc.php by setting _PS_MODE_DEV_ to true. It shows the real error instead of the blank page. Remember to turn it off right afterwards: in production it exposes information useful to attackers.

How much does it cost to get the store back up?

It starts from €149, which covers diagnosis and fix of a single cause on one store, during office hours. We set the price in the quote, free of charge, before we start. Development, for example fixing a custom module, server work and an emergency start are not included: if they're needed we stop and update the quote before going ahead.

Could the outage be an attack?

Sometimes: modified files, unknown admin users or odd redirects are signs of an infection. In that case we stop and move to malware removal, which is quoted separately, instead of putting a compromised store back online.

Do you work out of hours?

Office hours are Mon-Fri 09:00-18:00. With an on-call plan we pick up a store that is down within one hour even out of hours, at the office rate. Without a plan we still pick it up within 24 hours, weekends and public holidays included, at the out-of-hours rate set out in the terms, if we already work together.

The store works but the back office won't open: is it the same job?

Yes. A blocked back office has the same causes as a blocked store: a module loading in the admin pages, the cache, an override or the PHP version. The diagnosis is done the same way, from the logs, and the starting figure is the same.

The host updated PHP and the store broke: what do you do?

First we put the store back online, usually by taking PHP back to the version the store supports, if the host allows it. Then we tell you what's needed to run on the new version: often it's a PrestaShop or module update, which is quoted separately, because staying on an unsupported PHP is not a solution.

Other fixes

PrestaShop fixes and maintenance →
quote.service

Is your PrestaShop store in trouble?

Tell us what's happening: we reply within one working day with the likely cause and the price.

Get in touch

from €149price set in the quote

Request this fix →
Book a 30-minute call
Open in a new tab