Difference between revisions of "Provisioning Issues"

From WHMCS Documentation

(Product Provisioning Problems)
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page provides the explanations and solutions to general errors which may occur with multiple modules. For troubleshooting and debugging instructions please refer to [[Auto Setup Issues]]. For specific errors relating to individual modules, please refer to the Troubleshooting section of the corresponding module's documentation page:
+
This page provides information about general errors that may occur with multiple modules.  
  
===Hosting accounts aren't provisioned automatically===
+
For specific errors relating to individual modules, see the Troubleshooting section of the corresponding [[Server_Modules|module's documentation page]].
[[File:Videotutorial.png‎|center|link=http://www.youtube.com/watch?v=Ug3wbYRpUgI|Watch Video Tutorial]]
 
  
 +
== Product Provisioning Problems ==
  
Please review '''Utilities > Logs > Activity Log''' at the time of account creation for any error messages, the most common errors are explained further down this page and on the corresponding module's documentation page:
+
WHMCS can automatically provision services either before or after payment or can wait until a staff member manually approves it or disables it entirely.
  
*[[Server Modules]]
+
To set this on a per-product basis, use the '''Module Settings''' tab when editing a product at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Products and Services|Products/Services]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Products/Services'''.
*[[Domain_Registrars]]
 
  
===Server Command Error - Curl Error - Couldn't resolve host (6)===
+
If setup does not occur automatically, see [https://help.whmcs.com/m/troubleshooting/l/679718-troubleshooting-product-provisioning-problems Troubleshooting Product Provisioning Problems]. This includes help with the following errors:
This error message indicates that you don't have a server selected for the account to be setup on. There are a few points you should check:
 
  
* Ensure you have a default server set in Setup > Products/Services > Servers (denoted by an asterisk *) and that a server is selected on the account that you are trying to setup.
+
* <tt>Server Command Error - Curl Error - Couldn't resolve host (6)</tt>
 +
* <tt>Server Command Error - Curl Error - Couldn't connect to host (7)</tt>
 +
* <tt>Required Product Module <nowiki>''</nowiki> Missing</tt>
 +
* <tt>Allowed memory size of xxxxx bytes exhausted</tt>
 +
* <tt>Server Command Error - Curl Error - 28 connect() timed out</tt>
 +
* <tt>406 Not Acceptable</tt>
  
* If a server group has been configured ensure at-least one server has been added to the group.
+
== Domain Provisioning Problems ==
  
* The module selected under Setup > Products/Services > Servers is the same as the module selected under Setup > Products/Services > Products/Services > Edit > Module Settings tab.
+
WHMCS can automatically register or transfer domains after the client has paid the invoice. You can either specify the registrar to use for this automation or disable the automation entirely per-domain at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Domain Pricing]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Domain Pricing'''.
  
===Server Command Error - Curl Error - Couldn't connect to host (7)===
+
If you have selected a registrar in the steps above but the system didn't send the domain to the registrar upon payment, an error has occurred. Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' or, prior to WHMCS 8.0, '''Utilities > Logs''' at the time of ordering for any error messages, which will explain what the problem is. You can find an explanation of common error messages at:
Getting this error means that you have a firewall on your server blocking the connection. The port being used depends upon the module in use but for cPanel it would be 2086/2087, Plesk 8443, DirectAdmin 2222, etc... open for inbound and outbound connections on both the server WHMCS is installed on and the remote server being connected to. Please contact your server admin/hosting provider to open those ports.
 
  
===Other Module Command/Registrar Error===
+
*[[Troubleshooting Guide]].
Steps for identifying the cause of other Module Command or Registrar Command errors can be found in our [[Troubleshooting Guide]].
+
*[[Common Troubleshooting Tips]].
 +
*[[Domain Registrars]].
  
===Required Product Module <nowiki>''</nowiki> Missing===
+
To submit the domain registration or transfer request to your registrar again, see [[Domains_Management#Handling_a_Failed_Domain_Registration|Handling a Failed Domain Registration]].
This error message indicates that a module command was performed for a product to which no module is assigned. Please navigate to '''Setup > Products/Services > Products/Services > Edit > Module Settings tab''' and ensure the appropriate module is selected.
 
  
If the module selection has intentionally been left at None, then you may wish to consider using the [[Auto Release]] module instead. With the [[Auto Release]] module, WHMCS can open a support ticket or create a to-do list entry when a module command is performed to notify you that manual action is required.
+
==Welcome Email Sending Problems==
  
===Allowed memory size of xxxxx bytes exhausted===
+
Problems sending welcome emails typically relate to the account creation issue above. The system sends the welcome email when the module's '''Create''' command completes successfully and automatically, creating the account on the server. Unsent welcome emails indicate a problem with the automated setup not occurring.
An error message along the lines of "''Allowed memory size of xxxxx bytes exhausted (tried to allocate xxxx bytes)''" means that WHMCS has reached maximum amount of memory available per the memory_limit setting in your server's PHP configuration. You should increase this setting until the error is resolved - contact your server admin/hosting provider for assistance making this change.
 
  
Please take this opportunity to ensure all the other [[System Requirements]] are met.
+
For steps to troubleshoot this, see [[Email Sending Issues]].
  
===Server Command Error - Curl Error - 28 connect() timed out===
+
==Other Module Command/Registrar Error==
This error message means that the operation you were attempting to perform timed out. Some common causes of timeouts in WHMCS are:
 
  
* Server too busy dealing with other requests
+
For steps to identify other module command or registrar command errors, see [[Troubleshooting Guide]].
* Server taking more than 150 seconds to provision the account
 
* Server site IP address does not match the server details entered into WHMCS
 
* Server doesn't exist
 
  
In order to resolve this you must ensure:
+
{{troubleshooting}}
 
 
* There is no firewall on your server blocking the requests from WHMCS
 
* Enable/disable SSL mode on your servers by going to ''Setup > Products/Services > Servers > Edit''.
 
 
 
===Server load, uptime and phpinfo always say Unavailable or 00:00:00===
 
In order for these values to be obtained, the file /status/index.php that you upload to every server has to be able to execute the PHP functions exec and shell_exec on that server.  These are often disabled by default for security reasons.  To enable them, you need to login to your server by SSH and then locate the php.ini file and open it for editing.  Search down for the line that says disabled_functions and then remove exec and shell_exec from the list of functions following that.
 
 
 
For security, by default the phpinfo is disabled, you would need to edit the index.php file of the status directory and uncomment the phpinfo(); line,
 

Latest revision as of 20:03, 23 November 2022

This page provides information about general errors that may occur with multiple modules.

For specific errors relating to individual modules, see the Troubleshooting section of the corresponding module's documentation page.

Product Provisioning Problems

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

To set this on a per-product basis, use the Module Settings tab when editing a product at Configuration () > System Settings > Products/Services or, prior to WHMCS 8.0, Setup > Products/Services > Products/Services.

If setup does not occur automatically, see Troubleshooting Product Provisioning Problems. This includes help with the following errors:

  • Server Command Error - Curl Error - Couldn't resolve host (6)
  • Server Command Error - Curl Error - Couldn't connect to host (7)
  • Required Product Module '' Missing
  • Allowed memory size of xxxxx bytes exhausted
  • Server Command Error - Curl Error - 28 connect() timed out
  • 406 Not Acceptable

Domain Provisioning Problems

WHMCS can automatically register or transfer domains after the client has paid the invoice. You can either specify the registrar to use for this automation or disable the automation entirely per-domain at Configuration () > System Settings > Domain Pricing or, prior to WHMCS 8.0, Setup > Products/Services > Domain Pricing.

If you have selected a registrar in the steps above but the system didn't send the domain to the registrar upon payment, an error has occurred. Review Configuration () > System Logs or, prior to WHMCS 8.0, Utilities > Logs at the time of ordering for any error messages, which will explain what the problem is. You can find an explanation of common error messages at:

To submit the domain registration or transfer request to your registrar again, see Handling a Failed Domain Registration.

Welcome Email Sending Problems

Problems sending welcome emails typically relate to the account creation issue above. The system sends the welcome email when the module's Create command completes successfully and automatically, creating the account on the server. Unsent welcome emails indicate a problem with the automated setup not occurring.

For steps to troubleshoot this, see Email Sending Issues.

Other Module Command/Registrar Error

For steps to identify other module command or registrar command errors, see Troubleshooting Guide.