A cPanel connection lets the suite read and manage the hosting accounts attached to your WHMCS services. WHMCS stores the server login; Hosting Suite adds the provider profile, account verification and product-level controls.
IN THIS ARTICLE
01 Prepare the WHM connection
Use a hostname with a valid HTTPS certificate and the correct secure WHM port, normally 2087. The WHMCS server must be able to reach it. In WHM, create a dedicated API token under Development > Manage API Tokens using the root or reseller identity that legitimately owns the accounts you manage.
Choose permissions for the workflows you intend to offer. Reading accounts, invoking account APIs, creating sessions and changing hosting packages are different permissions. A token that can list accounts may still be unable to launch WP Toolkit or create customer sessions. Restrict its source addresses where practical and record its expiry for rotation.
02 Configure WHMCS and the suite
- Open System Settings > Servers in WHMCS and save the server hostname, secure port, username and supported API-token credential.
- Open Workspace > Suite settings > Hosting platforms in the suite and enable cPanel.
- Open Account Manager > Hosting platforms, find the server and choose Connection profile.
- Select cPanel. Under Read the login from, choose automatic detection or API token / access hash as appropriate to the WHMCS server fields.
- Save the profile, then verify a known service under Existing accounts.
- Enable that product's required features and open its account workspace. Check the domain, mailboxes and usage before testing a change.
Which cPanel tools should I enable for a product?
The account's cPanel package and feature list determine additional capabilities. Terminal requires SSH access and an actual shell. WP Toolkit, Softaculous, CloudLinux's PHP Selector and server backup or security integrations have their own availability and licensing requirements. Product switches cannot install a missing server component.
A service using the cpanelextended module name is recognised as cPanel, but confirm how your existing provisioning module and hooks work together before enabling overlapping customer workflows.
03 Verify and troubleshoot
For an authentication error, inspect the WHMCS server credential, token expiry, source-IP restrictions and required privileges. For an account mismatch, fix the service's server, username or main domain instead of weakening the check. After changing the connection profile, verify affected account links again. For an uncertain write result, refresh the remote list before repeating it; the action may already have completed.