Healthchecks

Run an automated checklist for your system’s health. This checklist helps detect unusual or unsupported setups, as well as systems restored in a different environment.

Notable features include:

• New in 2.0.0: Additional documentation linking detailed information that explains the reason and rationale behind specific health checks
• New in 2.0.0: Detects if a newer release of Healthchecks is available (via an anonymous request retrieving release information)
• New in 2.0.0: Checks whether all required configuration is set when Liferay cookie handling is enabled (remains quiet for external cookie handling)
• New in 2.0.0: Detects deactivated CAPTCHA in relaxed security configurations
• New in 2.0.0: Checks if Headless API Explorer is disabled in production setups
• New in 2.0.0: Allows whitelisting HTTP probes (non-HTTPS) from defined sources, with defaults suitable for Liferay PaaS setups
• New in 2.0.0: Makes existing health checks aware of relaxed (non-production) security settings when configured, improving usability on such systems
• New in 2.0.0: Available for DXP-2025-Q4 (contact the author to obtain this version, as Marketplace currently does not allow publishing for this version)
• Runs VerifyProperties for your version at runtime
• Checks the age of your installation, taking your LTS preference into account (some checks are DXP-specific and the desired age is configurable)
• Performs user password hashing checks, including a configurable sample size of users to verify up-to-date hashing strength
• Validates correct configuration of boolean and numeric properties
• Detects if a backup has been restored on a different system (e.g., PRD restored in UAT), prompting administrators to review related configurations such as Client Extensions, Data Providers, and Web Hooks
• Verifies correct redirection rules for accessed hostnames
• Displays the remaining Premium Support period (DXP only) and warns a configurable time before expiration
• Allows defining the minimum expected number of nodes in a healthy cluster
• Checks the validity of TLS certificates for connected systems (Client Extensions, Data Providers, Web Hooks, or a manually configured host list)
• Provides optional relaxed settings for development systems (hostnames must be explicitly specified) to improve development experience
• Detects if the search index is outdated and requires reindexing (by sampling indexed users)
• Identifies unsupported configurations (e.g., HSQL or Elasticsearch Sidecar)
• Detects if the server started with incomplete components (smoke-test/beta) and requires a restart
• Verifies whether ImageMagick is correctly configured to enable AVIF and WEBP image formats, including Adaptive Images and Previews
• Uses “localhost” as the default relaxed setting, assuming development environments where convenience is preferred (configurable in System and Instance Settings)
• Validates Fragments for potential SPA-related problems, including optional whitelisting via checksum and JavaScript comments
• Supports the Jakarta EE release 2025-Q3
• Bugfix in 1.0.6: Ignoring expired TLS certificates now applies only to a specific certificate’s not-valid-after date and no longer to all future certificates for the same domain
• Detects if Data Sets were activated in Beta before official release and notifies users about required data cleanup