Get the Best WordPress Backup
& Migration Plugin Today
Get Duplicator Now

Duplicator Documentation

Documentation, Reference Materials, and Tutorials for Duplicator

How to fix installer validation checks?

When running the installer, validation checks are performed to detect any potential issues that may affect the installation process. These checks help identify problems related to file systems, PHP configuration, and other important factors before proceeding with installation.

This article explains what the validation checks mean, how to interpret the status codes, and how to address common issues such as file permission problems caused by Imunify360.

Understanding validation status codes

The installer uses color-coded status indicators to help you quickly understand any issues found during validation. Below is a breakdown of the different status levels:

StatusDescription
PassThe check passed successfully; no issues detected.
NoticeA minor issue detected with low risk. You can proceed with the installation. If problems arise, consider resolving this notice.
WarnAn issue detected with a high risk of causing installation problems. It is recommended to address this issue before proceeding.
FailA critical issue found. Installation cannot proceed until the issue is resolved.

General checks

General validation checks are performed to ensure a stable installation environment. These are fully detailed within the installer interface, and no additional guidance is required from this article.

File System checks

This section focuses on file system validation checks, specifically permissions issues that can block a successful installation.

Issue: Permissions problem caused by Imunify360

During archive extraction, you may encounter permission-related warnings, often linked to Imunify360. Continuing with installation under these conditions may result in log errors such as:

Common error messages

  • FILE CORE EXTRACTION ERROR: wp-includes/class-oembed.php (or similar file path)
  • MSG: touch(): Unable to create file /some_path/ No such file or directory
  • Invalid glob header marker OR Invalid header marker

Solution: Adjusting Imunify360 settings

This problem often occurs because of a security tool called Imunify360, commonly installed by hosting providers. Its “Proactive Defense” feature, set to “Kill” mode by default, can mistakenly identify the installer file as malicious, preventing proper installation.

Steps to resolve the issue

  1. Log in to your cPanel or hosting control panel.
  2. Open the Imunify360 application.
  3. Navigate to the Proactive Defense section.
  4. Change the Mode Settings to Disabled or Log Only.

Once Proactive Defense is disabled, proceed with the installation. After completion, you can re-enable Proactive Defense if desired.

Note: If you do not see an Imunify360 option in your hosting panel, contact your hosting provider and request that they temporarily disable the Proactive Defense feature to allow the installation to proceed.

For more detailed instructions, refer to this guide: Disable Imunify360 in cPanel.

PHP Config and Database Checks

PHP configuration and database checks are included in the validation process and are fully explained within the installer. No additional troubleshooting is needed from this article.

Was this article helpful?

Related Articles