To install Magento 2 on Flashcloud: set the right PHP version first, install via Composer over SSH, then point the domain's document root at Magento's pub folder. Magento isn't a one-click Softaculous install, it's a manual Composer-based setup.
Magento 2 has hard PHP version requirements, needs Composer to pull its dependencies, and expects specific PHP extensions and memory limits that most shared installers don't set correctly out of the box. Flashcloud's stack (LiteSpeed, NVMe storage, PHP 7.4 through 8.3) supports Magento, but it has to be configured deliberately.
Set the PHP version first
Magento 2 releases each target a narrow band of PHP versions, and installing on the wrong one will fail partway through Composer or throw fatal errors on first load. Check the version number of the Magento release you're installing against its official compatibility matrix before you touch anything else.
On Flashcloud, switch the domain's PHP version from the PHP Version tile in the portal (Services → your hosting). That tile only changes the version, 7.4 through 8.3. The extensions Magento needs (things like the OPcache, Imagick, and Intl extensions) are managed separately in cPanel's Select PHP Version tool, where you can toggle individual PHP extensions on for your account.
Memory and upload limits are a common early blocker too. Magento's installer and Composer both want generous memory_limit and upload_max_filesize values. Change those in cPanel under Software → MultiPHP INI Editor, in Editor mode, scoped to your domain's document root.
Install with Composer over SSH
Magento's own installer expects a Composer-based install, pulling packages straight from the Magento Marketplace (formerly Magento Connect). You'll need an SSH connection and a Magento Marketplace public/private authentication key pair, generated from your Adobe Commerce Marketplace account.
Manage your keys in cPanel's SSH Access tool and connect using an external SSH client, as cPanel does not offer an in-browser terminal tool, then run something like:
composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento2
When prompted, use your Marketplace public key as the username and the private key as the password. Composer will pull down the full dependency tree. On typical shared hosting resources, this takes a few minutes.
Once the files are in place, run Magento's CLI installer:
cd magento2 bin/magento setup:install \ --base-url=https://yourdomain.com/ \ --db-host=localhost \ --db-name=yourdbname \ --db-user=yourdbuser \ --db-password=yourdbpass \ --admin-firstname=Admin \ --admin-lastname=User \ --admin-email=admin@yourdomain.com \ --admin-user=admin \ --admin-password=yourpassword \ --language=en_US \ --currency=USD \ --timezone=America/New_York \ --use-rewrites=1
Create the database and database user beforehand from phpMyAdmin, or from the portal's MySQL Databases tile.
Point the domain at the right folder
Magento's web root is the pub subfolder inside the install, not the install's top-level directory. If you installed Magento into a subfolder under your main domain's document root, either move the install up and adjust, or set the domain (or an addon domain, from the Addon Domains tile) to serve directly from that pub folder. Serving from the wrong directory is the most common reason a fresh Magento install shows a directory listing or a 403 instead of the storefront.
Caching and performance
Magento is heavy, and it leans hard on caching to feel fast. It ships with its own two-level cache system (Zend/Symfony cache pointed at Redis, ideally) plus a full-page cache layer. Flashcloud's stack already runs LiteSpeed with LSCache, but Magento's own cache configuration is separate from the LiteSpeed-for-WordPress stack described in how we make your site fast and the cache stack we ship with every WordPress install, those articles cover WordPress specifically, not Magento's own cache backend. For Magento, set the cache backend in app/etc/env.php to use Redis if it's available on your plan, then run bin/magento cache:enable once the site is confirmed working.
After installation, always run Magento in production mode for a live store:
bin/magento deploy:mode:set production
This compiles static assets ahead of time instead of generating them on each request, which matters a lot for page load speed under real traffic.
DNS and going live
If you're pointing a new domain at this install, or moving an existing Magento store to Flashcloud, get the domain's nameservers set to Flashcloud's first. The exact steps depend on where the domain is registered, see changing nameservers at GoDaddy, Namecheap, and Cloudflare for the walkthrough at the three most common registrars.
When to open a ticket
Composer dependency conflicts, extension-specific installation errors, and Magento version compatibility questions are common enough that it's worth opening a ticket from the portal (Support) if you get stuck partway through. Include the exact error message so it can be looked into directly.