A Magento server and a completed Magento store are separate deliverables. Check your order and service handover for the installed application, control panel and support scope. Repository access is needed for certain installation methods; it is not a requirement for buying or connecting to a server.
1. Choose the correct path
- Already installed: use the supplied application URL and check the store. Do not run a new installation over it.
- Existing store: migrate its database, media, application code, configuration and encryption key using matching versions. Keep the original available until verification succeeds.
- Fresh store: use a supported installer already included with your panel, or Adobe's official Composer installation method. The existence of this guide does not mean a panel or installer licence is included.
2. Prepare a fresh installation
Choose a maintained Magento Open Source release and check Adobe's exact compatibility table for PHP, database, search engine and other dependencies. Do not choose each component's newest version independently. Use a dedicated application filesystem owner and private database/search services.
For the official Composer path, obtain your own repository access keys through Adobe Commerce Marketplace. Magento Open Source and paid Adobe Commerce are different editions. Protect any Composer authentication file outside public web content; never send keys in chat or publish them in a repository.
- Follow the official Composer guide linked below to download the selected Open Source metapackage into an empty application directory.
- Set ownership and permissions for the web server and filesystem owner. Do not use chmod 777 as an installation fix.
- Configure the HTTPS domain, database and compatible search service. Use the official CLI installation options for your version, with unique administrator credentials.
- Keep the web document root at the application's pub directory. Complete cron, indexing, production configuration and administrator two-factor authentication.
3. Verify before accepting customer orders
From the installed application's root, as its filesystem owner, use:
Run each command separately:
php bin/magento --version
php bin/magento setup:db:status
php bin/magento indexer:status
php bin/magento cache:status
Open the storefront and administrator login over HTTPS. Check category navigation, product search, images and a test cart. Use the payment provider's sandbox for checkout testing; do not treat an administrator login as proof that payments or order emails work. Inspect scheduled jobs and search-service errors.
4. Common failures
A Composer authorisation error concerns repository credentials or edition entitlement, not your VPS login. Search connection failures require checking the selected engine, version, network and authentication. Missing styles often concern static assets or filesystem permissions. Preserve logs and a backup before applying changes.
Next: Backups and restore checks.
Official references
Technical guidance reviewed: 28 October 2026. Match instructions to your actual service and application version.
