When VirtFusion WHMCS provisioning fails, the customer pays but no VPS appears. Almost every failure is explained in the WHMCS module log, and most come down to a token, an ID mismatch or a lack of capacity.
Before you start
- WHMCS admin access with permission to view logs and run module commands.
- VirtFusion admin access to compare package, group and template IDs.
- The failed order or service ID.
Read the module log
- Open WHMCS → Configuration → System Logs → Module Log (older versions: Utilities → Logs → Module Log) and enable module logging.
- Run the action again from the service page with Module Commands → Create.
- Open the module log and find the VirtFusion entry. Read the request and the response body.
Tip: Turn module logging off again after debugging; it can record sensitive data.
Common VirtFusion WHMCS errors and fixes
| Error in log | Likely cause | Fix |
|---|---|---|
| 401 / Unauthenticated | Bad or revoked API token | Create a new token and update the WHMCS server entry |
| Package not found | Wrong package ID in product settings | Copy the correct ID from VirtFusion Packages |
| Hypervisor group not found | Wrong group ID | Correct it in the product's module settings |
| No hypervisor with capacity | No node has free RAM, disk or IPs | Add capacity or IPs, then retry |
| Invalid OS template | Configurable option points to a removed template | Update the option values to existing template IDs |
| Connection timed out | WHMCS cannot reach the panel | Check DNS, firewall and SSL on the control server |
Check the user mapping
- The module creates or links a VirtFusion user for each WHMCS client, usually by email or an external ID.
- If a VirtFusion user with that email already exists from a manual setup, linking can fail; merge or adjust the user record.
Retry and confirm
- After fixing the cause, run Create again from the service.
- Confirm the server appears in VirtFusion under the right user.
- Send the welcome email manually if the automatic one was skipped.
Troubleshooting automation
- Create never runs: check the product's module settings → automatically setup option and that the WHMCS cron runs every few minutes.
- Duplicate servers: the create was retried after a timeout that actually succeeded. Check VirtFusion before retrying.
Frequently asked questions
Should I update the WHMCS module with VirtFusion?
Yes. Use the module version that matches your panel release.
Can I link an existing VirtFusion server to a WHMCS service?
Yes, by entering the server ID in the service's module custom fields.
Why does the customer not see their VPS in WHMCS?
The service may still be pending or the create failed; check its status and the module log.