Troubleshooting Product Provisioning Problems

Symptom

WHMCS can automatically provision services either before or after payment or can wait until a staff member manually approves it or disables it entirely.

You can set this on a per-product basis in the Module Settings tab at Configuration > System Settings > Products/Services (Setup > Products/Services > Products/Services.

However, in some cases, automatic provisioning may not function due to one of several issues.

Cause

Reviewing the logs from the time of the order can help you find associated errors.

To do this, go to Configuration > System Logs (Utilities > Activity Log prior to WHMCS 8.0) and check for error messages at or near the time of the order.

We also recommend reviewing this video tutorial.

Server Command Error - Curl Error - Couldn't resolve host (6)

This error indicates that the account doesn't have an associated server.

Check for the following issues in the Servers tab while editing a product group at Configuration > System Settings > Products/Services or, prior to WHMCS 8.0, Setup > Products/Services > Products/Services:

  • You have set the correct servers and, if using a server group, Configuration > System Settings > Servers or, prior to WHMCS 8.0, Setup > Products/Services > Servers lists at least one server for that server group.
  • The module is the same module that you selected in the Module Settings tab for the individual products.

Server Command Error - Curl Error - Couldn't connect to host (7)

This error indicates that a firewall on your server is blocking the connection. The port depends on the module in use:

cPanel 2086 and 2087
Plesk 8443
DirectAdmin 2222

Leave these ports open for inbound and outbound connections on the WHMCS server and the remote server. For assistance, contact your hosting provider or system administrator.

Required Product Module '' Missing

This error message indicates that the system performed a module command for a product without an assigned module.

Go to the Module Settings tab for a product at Configuration > System Settings > Products/Services or, prior to WHMCS 8.0, Setup > Products/Services > Products/Services to check the module setting.

Instead of selecting None for the module, we recommend using the Auto Release module. This module lets WHMCS open a support ticket or create a to-do list entry when a module command occurs and manual action is required.

Allowed memory size of xxxxx bytes exhausted

This error message indicates that WHMCS has reached the maximum amount of memory in the memory_limit setting in your server's PHP configuration. Adjust this setting until the error is resolved.

For assistance, contact your hosting provider or system administrator.

Server Command Error - Curl Error - 28 connect() timed out

This error indicates that the attempted operation timed out. There are several common causes of this issue:

  • The server is too busy dealing with other requests.
  • The server required more than 150 seconds to provision the account.
  • The server's site IP address does not match the server details in WHMCS.
  • The server doesn't exist.

In order to resolve this, make certain that:

  • Your firewalls aren't blocking requests from WHMCS.
  • You have correctly configured SSL mode for the server at Configuration > System Settings > Servers or, prior to WHMCS 8.0, Setup > Products/Services > Servers.

406 Not Acceptable

This error is usually due to the server's mod_security rules blocking the query from WHMCS. To resolve this, check the mod_security log for the triggered rule and that rule.

If you do not have access to the server's mod_security log or to change the rule configuration, contact your server administrator or hosting provider.

Other Errors

You can find information about other common error messages at:

Retrying the Module Action

After you have resolved the error, perform the following steps to retry the module action:

1. Navigate to Utilities > Module Queue.

2. Find the service.

WHMCS - Module Queue

3. Click Retry.

Click Retry

The system will attempt the action again.

If an error displays, repeat the above steps to address the problem and retry the action again.