Virtualizor

Fix Virtualizor WHMCS provisioning errors

Troubleshoot the Virtualizor WHMCS module when orders fail: read the module log, fix API credentials, plan and server group mapping, IP pool shortages and OS template IDs.

AdvancedWHMCS2 min read

When Virtualizor WHMCS provisioning fails, the order is paid but the VPS is not created, and the customer is waiting. The WHMCS module log nearly always names the cause, which is usually credentials, mapping or a lack of free resources.

Before you start

  • WHMCS admin access and Virtualizor admin access.
  • The service ID of the failed order.

Read the module log

  1. Open WHMCS → Configuration → System Logs → Module Log (older versions: Utilities → Logs → Module Log) and enable logging.
  2. On the service page, run Module Commands → Create again.
  3. Find the Virtualizor entry and read the response text.

Common Virtualizor WHMCS errors

Symptom in logCauseFix
Authentication / API failedWrong API key or pass, or WHMCS IP not allowedRecheck credentials and the allowed IP list (admin API keys)
Could not connectPort 4085 blocked, wrong hostnameOpen the port to the WHMCS IP and test with curl
Plan not foundProduct points to a deleted or renamed planReselect the plan in the product's Module Settings
No IP availableThe IP pool for the server is emptyAdd IPs to the pool (IP pools and templates)
No server with enough resourcesNode or server group fullAdd capacity or change the server group
OS template not foundConfigurable option value points to a removed templateUpdate option values to existing template IDs

Tip: Check Virtualizor before retrying. If the create actually succeeded after a timeout, a retry makes a duplicate VPS.

Check module settings

  • The product's Module Settings tab uses the right server group and plan, and the virtualisation type (KVM, OpenVZ and so on) matches the node.
  • Configurable options and custom fields use the names the module expects; re-run the module's option creation if they were edited by hand.
  • The Virtualizor WHMCS module version matches your Virtualizor version.

Retry and finish

  1. Fix the cause and run Create again.
  2. Confirm the VPS exists in Virtualizor under the client's user.
  3. Resend the welcome email if needed.

Frequently asked questions

Why does create not run automatically?

Check the product's automatic setup option and that the WHMCS cron runs regularly.

Can I link an existing VPS to a service?

Yes, by entering the VPS ID in the service's module fields, as described in the module documentation.

Where do customers manage the VPS?

From the WHMCS service page, which opens the Virtualizor panel through single sign-on.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.