This guide applies to Pimcore 11 (Symfony-based) and PHP 8.1 or higher. You need a live24h account, a workspace and an API key with write permission – see the shared steps .
Install
Composer installation and bundle activation:
composer require live24h/pimcore-adapter
Enable the bundle in config/bundles.php:
return [
// ...
Live24h\PimcoreAdapter\Bundle\Live24hHealthCenterBundle::class => ['all' => true],
];
Import the routing in config/routes.yaml:
live24h_health_center:
resource: '@Live24hHealthCenterBundle/Resources/config/routing.yaml'
Then install the bundle, clear the cache and grant the appropriate back-end role the ACL permission live24h_health_center:
bin/console pimcore:bundle:install Live24hHealthCenterBundle
bin/console cache:clear
Step by step
The flow matches the illustrated path in the overview ; for Pimcore it works as follows:
- In the Pimcore back end, open the live24h Health Center menu item (
/admin/live24h-health-center). - In the Settings tab, enter the API key and test the connection (“Test connection”). The key is always shown masked (
lv24_••••<last4>). - Start the analysis of your Documents and Sites.
- Review the Website Health Score and the recommendations – grouped by SEO, SSL/domain/DNS and mail deliverability.
- Select the checks. Locked suggestions stay visible and are marked “From Pro”.
- Create the selected checks in live24h with one click.
With the policy presets Essential, Recommended and All, you control the scope of the pre-selection. A dry run writes nothing and only shows the report.
Troubleshooting and tips
The “live24h Health Center” menu item is missing.
Check whether the bundle is enabled in config/bundles.php and the routing is imported in config/routes.yaml. Run bin/console pimcore:bundle:install Live24hHealthCenterBundle and clear the cache with bin/console cache:clear. Also make sure your back-end role has the ACL permission live24h_health_center.
“Test connection” fails.
Check the API key (write permission required), the API base URL (https://api.live24h.eu) and whether the server is allowed to connect outbound. On failure, the connection deliberately stays closed (fail-closed) and follows no redirects.
The wrong or no domains are being checked. The domains are derived from the Pimcore Sites table. Set a unique productive root domain per site so that SSL, domain and DNS checks are mapped correctly.
The mail check suggests an item but creates no check. This is intentional: MX, SPF, DKIM and DMARC are shown for information. There is no mail check type, so the plugin deliberately suggests no creatable monitor for this.
Where is the heartbeat for maintenance or cron jobs? For Pimcore it deliberately does not exist. Pimcore offers no uniformly detectable cron model, so we honestly omit the heartbeat instead of showing an empty panel.
Frequently asked questions
Does the scan write anything into Pimcore? No. The scan is read-only and works cache-based. Only when you select and create checks is the configuration created on the live24h platform. With the preset as a dry run, nothing is written.
Are multiple Sites supported? Yes. Sites and domains are read from the Pimcore Sites table and can be protected per domain.
Are Assets and DataObjects taken into account? They appear as a content overview in the Health Center. Creatable checks come from the SEO, SSL, domain and DNS areas.