This guide applies to Magento 2.4.6 or newer (Adobe Commerce, Magento Open Source or Mage-OS) and PHP 8.1+. You need a live24h account, a workspace and an API key with write permission – see the shared steps .
Install
The module is installed via Composer and then enabled:
composer require live24h/module-health-center
bin/magento module:enable Live24h_HealthCenter
bin/magento setup:upgrade
bin/magento setup:di:compile
In production mode, additionally regenerate the static content and flush the cache:
bin/magento setup:static-content:deploy
bin/magento cache:flush
A listing in the official Adobe Commerce Marketplace will follow; until then, the module is available as a direct download from live24h.
Step by step
The flow matches the illustrated example in the plugin overview ; here are the Magento-specific paths:
- Open the configuration under Stores → Configuration → Services → live24h Health Center.
- Enter the live24h API key and leave the API Base set to
https://api.live24h.euunless support specifies a different environment. - Save and use the connection test.
- Open the Health Center under Stores → live24h Health Center.
- Start the scan across your stores and store domains.
- Review the Website Health Score, the plan notes and the suggestions.
- The checkout is pre-selected; cart and account are available as optional suggestions.
- Add SSL/domain per store domain, SEO signals, the cron heartbeat and the mail deliverability (MX/SPF/DKIM/DMARC) where needed.
- Select the checks and click Create – the checks are created in live24h.
The policy presets (minimal, ecommerce, enterprise) control how comprehensive the recommendation is – from a lean reachability set to the full commerce, cron and mail scope.
Troubleshooting and tips
The live24h Health Center is not visible in the admin.
Check whether the module is enabled (bin/magento module:status Live24h_HealthCenter), run bin/magento setup:upgrade and bin/magento setup:di:compile again if needed, and flush the cache with bin/magento cache:flush. 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, an active maintenance mode or an upstream full-page cache can block automated calls. Check whether the storefront paths are reachable without a login.
The cron heartbeat stays on “Waiting”.
This is normal and not an error: a heartbeat waits for the first signal from the monitored job. As long as the Magento cron (bin/magento cron:run) has not reported in yet, the check stays on “Waiting” – not on “Down”. With the first run, the status switches to “Operational”. Make sure the cron runs regularly via system cron or bin/magento cron:install.
Mail checks (SPF/DKIM/DMARC) report problems. Magento sends transactional mail through the configured store domain. Check the DNS records of that sender domain; missing SPF, DKIM or DMARC records are the most common reason why order and shipping mails don’t arrive.
The wrong store is being monitored. Select the correct store or store domain in the Health Center. Multi-store projects can create their own checks per domain.
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 the cron 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.
Can I monitor the Magento cron? Yes. The cron can be protected as a heartbeat, so silent failures in indexing, transactional mail and jobs don’t only surface days later.