The Plesk integration manages the subscription or webspace associated with a WHMCS service. Correctly identifying that subscription is essential because one Plesk server can contain multiple customer accounts, subscriptions and system users.
IN THIS ARTICLE
01 Prepare the connection
Save the Plesk server in WHMCS with its HTTPS hostname, secure port, normally 8443, and a login or secret key that is allowed to use the XML API for the relevant subscriptions. The suite's account adapter uses Plesk's XML API. Enabling a REST API key alone is not a complete test of the XML connection.
For a secret key restricted by source address, use the actual outbound address of the WHMCS server. Confirm that Plesk's certificate validates for the saved hostname and that network rules permit the connection.
02 Link a representative subscription
- In Workspace > Suite settings > Hosting platforms, enable Plesk.
- Open Account Manager > Hosting platforms and edit the server's Connection profile.
- Select Plesk and the appropriate Read the login from option. Credentials remain in WHMCS Servers.
- Check the test service's server, main domain and hosting system username in WHMCS.
- Open Existing accounts and choose Verify and link. The subscription domain and hosting login must match.
- Enable the intended product features and open Open account workspace. Confirm that only the subscription's own sites and mailboxes are listed.
03 Understand available functions
The common tools cover domains, subdomains, aliases, email accounts, databases, FTP accounts, account password, resource information and eligible sign-in. PHP and SSL information can be displayed, but the cPanel-specific PHP, SSL, file and cron editors are not automatically available on Plesk.
Release 1.0.40 does not expose an application installer for Plesk, and the separate application-product builder is cPanel-based. Do not publish Plesk APS installation instructions for this suite release. Database engine choices also depend on what is installed on the Plesk server.
What should I check when a Plesk service does not match?
If verification fails, distinguish the Plesk customer login from the subscription's hosting system login. The service username used for account matching must be the expected hosting login. A customer-level sign-in may be unavailable when the subscription is owned directly by an administrator or reseller and no safe customer login can be resolved.
Test a controlled mailbox or database action on a service you own before widening access. If it fails, review API permissions and the specific response. Do not substitute another subscription's identity merely to make verification pass.