The native WHMCS DirectAdmin module supports account provisioning and common lifecycle actions when the connected DirectAdmin account has the required permissions. Its setup is separate from enabling Nabtech Hosting Suite client-area features.
IN THIS ARTICLE
01 Prepare the server
Create the intended user package in DirectAdmin and record its exact name. Choose a reseller or other appropriately authorised account for WHMCS. Where a DirectAdmin Login Key is used, grant the API permissions needed for the actions you intend to support instead of copying an unrestricted credential between systems.
Confirm the management hostname, certificate and port. DirectAdmin commonly uses port 2222, but use the actual configured endpoint and the module's port override when necessary.
02 Add the connection and product
- In WHMCS, open System Settings and Servers, then Add New Server. Select DirectAdmin.
- Enter the hostname or IP, authorised username and the password or supported Login Key. Enable the secure connection option when the server is configured for it.
- Use Test Connection and resolve any authentication, certificate or firewall error. Save the server only after confirming the intended connection.
- Add the server to the appropriate server group and review its default status if needed.
- Open the hosting product's Module Settings. Select DirectAdmin, choose the server group and enter the exact package name from DirectAdmin.
- Test a new service and confirm the remote username, domain, package and limits before opening the product to normal orders.
03 Check supported access and actions
The native module documents actions including create, suspend, unsuspend, terminate, package and password changes, usage reporting and a client-area link. WHMCS Connect support is a separate capability and is not provided by this native module. Do not confuse that limitation with another addon supplying its own account access features.
What should I check when DirectAdmin rejects a module request?
Check the Login Key's allowed commands, source-IP restrictions and package ownership. Account synchronisation may need permissions beyond basic creation. Repeated failed logins can lead to IP blocking; correct the credential problem and have the server administrator review the specific WHMCS source address. Avoid broadly clearing security controls to make one connection pass.