This article talks about the solutions for the PHP version issues you might face when installing/upgrading Adobe Commerce on-premises using the Web Setup Wizard.
On Adobe Commerce on cloud infrastructure, please note that service upgrades cannot be pushed to the production environment without 48 business hours’ notice to our infrastructure team. This is required as we need to ensure that we have an infrastructure support engineer available to update your configuration within a desired timeframe with minimal downtime to your production environment. So 48 hours prior to when your changes need to be on production submit a support ticket detailing your required service upgrade and stating the time when you want the upgrade process to start.
The check fails because you are using an unsupported PHP version.
The PHP readiness check doesn’t display the PHP version as the following figure shows.
This is a symptom of incorrect cron job setup. For more information, see Set up cron jobs in our developer documentation.
The check reports the incorrect PHP version. Typically, this happens only to advanced users who have multiple PHP versions installed. In some cases, the readiness check fails; in other cases, it might pass.
If the PHP version reported by the readiness check is incorrect, it’s the result of a mismatch of PHP versions between the PHP CLI and the web server plug-in. Adobe Commerce requires you to use one version of PHP for both the CLI (which runs cron) and the web server (which runs the Commerce Admin, Component Manager, and System Upgrade).
We assume that if you have this issue, you’re an advanced user who has likely installed multiple versions of PHP on your system.
To resolve the issue, try the following:
$PATHenvironment variable for multiple paths to PHP.
which phpcommand to locate the first PHP executable in your path; if it’s not correct, remove it or create a symlink to the correct PHP version.
phpinfo.phppage to collect more information.