This guide applies to PrestaShop 8.0 or newer and PHP 8.1 or newer. You need a live24h account, a workspace and an API key with write permission – see the shared steps .
Install
You have two paths – via the back office or via Composer:
Back office: get the module as a direct download from live24h, then in the back office under Modules → Upload a module select the ZIP and install it.
Composer:
composer require live24h/prestashop-adapter
php bin/console prestashop:module install live24hhealthcenter
A listing in the PrestaShop Addons Marketplace will follow.
Step by step
You will find the illustrated flow in the overview ; the following steps are identical to the wizard shown there, just inside the PrestaShop back office.
- Open the live24h Health Center module via its own admin tab in the back office.
- In the Settings tab, enter the live24h API key.
- Leave the API Base set to
https://api.live24h.euunless support specifies a different environment. - Save and use the connection test.
- Start the scan for the shop and stores (storefront, cart and checkout per shop domain, catalog, SEO, SSL/DNS, mail and cron).
- Review the Website Health Score, the plan notes and the suggestions.
- Choose a policy preset (minimal, standard or enterprise) and look at the dry-run preview.
- Select the checks and create them in live24h with one click.
Alternatively via CLI
# Dry-run: shows scan, modules, score and suggestions as a report
php bin/console prestashop:module live24hhealthcenter:scan
# Create: creates the default suggestions
php bin/console prestashop:module live24hhealthcenter:scan --apply
Troubleshooting and tips
The “live24h Health Center” tab is not visible in the back office. Check whether the module is installed and enabled, and clear the PrestaShop cache (Advanced Parameters → Performance → Clear cache). After an update, a hard reload of the browser also helps.
“Test connection” fails.
Check the API key (write permission required), the API Base https://api.live24h.eu and whether the server is allowed to connect outbound. Hosting firewalls occasionally block outgoing requests.
The checkout check reports an error even though the shop works. Bot protection, rate limits or an active maintenance mode can block automated calls. Check whether the storefront paths are reachable without a login.
In multistore, the wrong shop domain is checked. The scan derives storefront, checkout and SSL per productive shop domain. Check in the PrestaShop multistore configuration that each store has a correct, productive domain set.
A heartbeat check stays on “Waiting”. This is normal and not an error: a heartbeat waits for the first signal from the monitored job (the ping to the heartbeat URL). As long as the cron run has not reported in yet, the check stays on “Waiting” – not on “Down”. With the first run, the status switches to “Operational”.
The cron heartbeat does not appear. The heartbeat suggestion requires that the cronjobs module is active or that a webcron triggers the scheduled tasks. Without a registered task, this item is omitted.
A suggestion is marked “From Pro”. The check type is not included in your plan. Locked suggestions stay visible; you can deselect them or upgrade your plan .
Frequently asked questions
Why isn’t a normal homepage check enough? Because a shop generates revenue across several paths. Checkout, cart, product pages and cron jobs can fail while the homepage still loads.
Does the plugin place real test orders? No. The focus is on safe reachability, signal and heartbeat monitoring – without real payments.
Does it work with multistore? Yes. Storefront, checkout and SSL are derived per productive shop domain, so every store is captured in the setup.