Installation, server setup, payments, licensing, automation and update guidance in one searchable knowledge center.
Search the complete setup and operations guidance, then open any section directly from the navigation.
Understand the main HexaPanel modules and the customer-to-provisioning workflow.
HexaPanel combines customer management, products, checkout, invoices, payment verification, hosting provisioning, support and reporting in one Laravel application.
The standard workflow is: create products and server mappings, configure payment credentials, publish plans, accept a customer order, verify payment, provision the hosting account and manage renewals from the admin area.
Prepare PHP, database, cron, storage and SSL before installation.
Use PHP 8.2 or newer, MySQL or MariaDB, required PHP extensions, a writable storage directory and an HTTPS-enabled domain. Composer is recommended for dependency maintenance.
Create the database before installation and keep the Laravel APP_KEY, database credentials, gateway secrets and signing private keys outside public web access.
Deploy the application, configure environment values and initialize the database safely.
Upload the authorized release to the application directory, configure the .env file, import or migrate the database, create the storage link and clear Laravel caches.
After installation, open the admin area, complete the storefront, gateway, server and automation settings, then run a test purchase and test provisioning before enabling production checkout.
Connect hosting servers and map plans to the correct WHM packages.
Add each server separately with its hostname, secure port, WHM username or API token, nameservers, shared IP and account limit. Test the connection before assigning products.
Map every sellable hosting plan to a valid WHM package. Keep automation disabled until a manual account creation test succeeds.
Run renewals, reminders, provisioning and recovery jobs reliably.
Configure the Laravel scheduler to run every minute. Use the Automation Center to confirm scheduler and queue-worker health.
Failed jobs should be reviewed before retrying. HexaPanel checks existing WHM accounts before retrying provisioning to reduce duplicate-account risk.
Configure test credentials, webhook verification and production checkout.
Start with Razorpay test credentials. Save the Key ID, Key Secret and Webhook Secret in the admin settings, then configure the displayed webhook URL in Razorpay.
Complete a test payment and confirm that the order, payment, license and customer dashboard records are created only after signature verification. Enable live checkout after the complete test passes.
Activate HexaPanel and keep the license-server signing keys synchronized.
Open License Verification in the billing admin panel, enter the issued license key and activate it on the production base domain.
The license client must contain the public key generated for the same product that signs the license-server response. Never place a private signing key inside a customer software package.
Protect data before applying controlled System Update packages.
Create a database and application-file backup before every update. Upload only packages built for the installed product and updater version.
Do not replace .env, storage data, customer uploads, release files or signing private keys unless an update explicitly requires it. Review the update result and run a focused smoke test after installation.
Diagnose SSL, API, cache, queue and provisioning issues in a safe order.
Confirm DNS and SSL first, then test the application URL and API status endpoint. Check Laravel logs, database connectivity, storage permissions, scheduler health and queue failures.
For license errors, compare product ID and signing-key ID on both systems. For provisioning failures, test the WHM connection and package mapping before retrying the job.
Launch a professional billing, provisioning and customer-management platform under your own brand.