Provisioning and pending module actions
Oct 15, 2026
Provisioning is WHBMP asking a server or registrar to do something: create an account, suspend it, unsuspend it, terminate it, register a domain.
When it runs
- Create: at the moment set by the product's Auto Setup rule (order placed, first payment, or when you accept the order), or when you press Create on the service by hand.
- Suspend and unsuspend: by the daily automation when an invoice is overdue and later paid, or by hand.
- Terminate: by the automation after the overdue limit or a cancellation request, or by hand.
- Domains: register, renew, transfer, update nameservers and contacts when ordered or changed.
Module commands on a service
Open a service and use Module Commands:
| Command | Does |
|---|---|
| Create | Creates the account on the server |
| Suspend | Suspends it |
| Unsuspend | Unsuspends it |
| Terminate | Removes it |
| Change Password | Sets a new password on the server |
For VPS services you also get Reboot, Start, Stop, Reinstall OS and Open Console.
Changing a service's status in WHBMP only changes WHBMP's record. Use the module commands to act on the server as well.
When an action fails
WHBMP never says an action worked when it did not. A failure:
- is shown to staff with the real reason,
- is saved under Pending Module Actions with the failure reason and the time of the last attempt,
- is recorded in Settings > System Logs > Provision.
Clients only ever see "An error occurred. Please contact support." The real reason is kept for staff.
Pending Module Actions
Open it from the action list on the dashboard, which shows how many items wait. Each row names the action (Create Account, Suspend Account, Register Domain, Update Nameservers and so on), what it was for, and why it failed.
- Fix the cause (wrong credentials, no free package, firewall, a missing domain contact).
- Press Retry on a row, or Retry All.
- When you have fixed it another way, press Mark Resolved.
Typical causes
- The server credentials changed or the API token was revoked: re-enter them and press Test Connection.
- The package name does not exist on the server: pick it again on the product.
- The username already exists on the server.
- The domain name has no DNS or the server rejects it.
- The registrar balance is too low or the contact data is incomplete.
Logs
Settings > System Logs has Activity, Provision, Payment Gateway and Mail logs with filters. Provision logs keep the request and the response, which is the first thing to read when something fails. Entries are pruned after the retention you set in General Settings.