Installing WHMCS on a compatible hosting account

Choose the production address and make HTTPS work first. Check the release-specific PHP and ionCube versions, database support, required extensions, memory and scheduled-task access. The PHP used by the website and the command-line cron job must both be compatible. A server advertising the newest PHP does not mean every WHMCS version supports it.

1. Download an official release using your authorised licence account. Review compatibility for themes and modules you plan to install. Keep beta releases in a separate test environment.
2. Create a dedicated database and database user through the hosting panel. Give the user the privileges required for the WHMCS database, without granting access to unrelated applications.
3. Upload the official application files to the intended directory using a secure method. Follow the release's instructions for preparing its configuration file and necessary writable locations.
4. Open the HTTPS installation URL and complete the checks. Enter the licence and database details, then create a strong administrator account.
5. Remove the installation directory when the installer instructs you to do so. Apply the official post-installation permissions and protect configuration and storage locations from public access.
6. Configure the system cron using the exact path and schedule shown by WHMCS. Verify that it runs with a compatible PHP binary and reports successful automation.
7. Complete general settings, authenticated outbound email, administrator security and backup arrangements.

Create a controlled test order and use a payment gateway's sandbox where supported. Verify invoice generation, email delivery, product configuration and an appropriate provisioning test. Registrar and server actions can create real costs, so use a supported test mode or a deliberately limited test product.

Record the requirement or error that failed. Check the selected PHP runtime, ionCube compatibility, database credentials and file permissions. Avoid solving permissions errors by making the entire installation publicly writable. Share logs privately with licence keys, passwords and customer information removed.

Keep a tested backup of both files and database, and establish an update process that checks module compatibility before changing the live portal.

• Choosing and activating a WHMCS licence
• Creating a backup plan you can actually restore
• Paying a Nabtech invoice using an approved payment method
• Understanding managed hosting responsibilities before you need support

• WHMCS: Install WHMCS
• WHMCS: System Requirements
• WHMCS: Enhancing Security