Starting Magento installation:
File permissions check...
[Progress: 1 / 1323]
Required extensions check...
I'm installing Magento by command line.
Apache log is empty, php log is empty.
My Software dependencies:
Please check the system requirements before proceeding.
It would help if you made sure many things like php version and php extensions listed under the links above are available on your system. You can check var/system.log and var/exception.log, and install.log for more details.
If you find our reply helpful, please give us kudos.
An award-winning North American Magento Development Agency That Delivers Powerful Results, Innovation, and Secure Digital Transformation.
WebDesk Solution Support Team
It seems that your Magento installation is stuck at the "Required extensions check" step. This step checks if all the required PHP extensions are installed and enabled on your server. If any required extension is missing or disabled, Magento installation will not proceed.
You can try the following troubleshooting steps:
Check PHP extensions: Verify that all the required PHP extensions are installed and enabled. You can check the required PHP extensions in the Magento documentation for your specific Magento version.
Check PHP configuration: Verify that your PHP configuration meets the requirements for Magento installation. You can check the PHP configuration requirements in the Magento documentation for your specific Magento version.
Check file permissions: Verify that all Magento files and directories have the correct file permissions. You can find more information about file permissions in the Magento documentation.
Clear cache: Clear the Magento cache by running the following command in your Magento root directory: bin/magento cache:clean
Check Magento logs: Check the Magento logs for any errors or warnings. You can find the Magento logs in the var/log directory.
If none of the above steps resolve the issue, you can try installing Magento using a different method or on a different server. Also, you can try installing an earlier version of Magento to see if the issue persists.