Why Account Provisioning Fails

When a paid order does not turn into a hosting account, the cause is almost always one of a short list. Check them in this order.

1. The package names do not match

The control panel package named on the WHMAZ package must exist on the server, spelled exactly the same. On cPanel, reseller-created plans are usually prefixed with the reseller username, for example reseller_starter rather than starter. This is the most frequent cause by a wide margin.

2. The API credentials are wrong or under-privileged

Re-run Test Connection on the server record. If it passes but provisioning still fails, the token authenticates but lacks account creation rights — generate a new one with the correct privileges.

3. The firewall is blocking the call

Your WHMAZ server must reach the control panel's API port outbound, and the control panel must accept it inbound. Test from the WHMAZ server:

curl -I https://your-whm-hostname:2087

4. The curl extension is missing

Without it, every API call fails silently. Confirm with php -m | grep curl.

5. The server is genuinely full

Account limits, disk quotas or a reseller account limit can all refuse a new account. Check the control panel's own logs.

Where to look next

WHMAZ writes API failures to application/logs/. Open the log for the day the order was placed and search for the customer's domain — the control panel's own error message is usually recorded verbatim, which tells you immediately which of the above applies.

Once fixed, retry provisioning from the order screen rather than asking the customer to order again.

Was this article helpful?