Configure and troubleshoot customer control panel login

1. Verify that the service is linked to the correct account on the correct WHMCS server. Check the main domain and account username before testing any login action.
2. Open the product's Hosting Suite feature settings and enable the relevant panel login option. Confirm that the provider platform and product are enabled.
3. Check that the test WHMCS user can access this client account and has the applicable product single sign-on permission. An administrator's successful test does not prove a restricted user's access.
4. Open the active service through the client area and select its panel login control. Confirm the resulting session belongs to the intended hosting account.
5. Sign out of the panel and repeat with a second test account. This catches accidental account mapping problems before general release.

cPanel uses the server's permitted session creation facilities. DirectAdmin requires usable login-key support and sufficient permissions. Plesk login depends on a suitable customer owner being resolvable; an administrator-owned or reseller-owned subscription may not provide the same customer login path. Webuzo uses its configured administration connection to reach the end-user context. Virtualmin needs a working connection with the permissions required by its implementation.

Keep panel credentials in the WHMCS server configuration. A display link should not contain a reusable password. Protect the server account and API key because the module acts with the rights they grant.

Application plans deliberately expose the selected application's tools without a general control panel login or hosting account password control. This differs from a regular hosting product. Webmail can still appear when email is included and supported. Do not add an unrestricted panel link solely to imitate a normal hosting layout.

First confirm that ordinary account information loads. If it does not, repair the server connection or account link before investigating single sign-on. If account information works, check the provider's session capability, user permissions and package features. Record the time, service and safe error text, then inspect the related provider or module log. Avoid repeatedly opening sessions while changing several settings at once. Test one corrected condition and verify the destination account again.

• Verify and link existing hosting accounts
• Configure Hosting Suite access rules and verify effective permissions
• Check which Hosting Suite tools each control panel supports
• Choose customer tools for application hosting plans

• DirectAdmin API access and login keys
• Plesk XML API secret keys