Difference between revisions of "Provisioning Issues"
(→Hosting accounts aren't provisioned automatically) |
|||
| 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 | + | This page provides the explanations and solutions to general errors which may occur with multiple modules. For troubleshooting and debugging instructions, see [[Auto Setup Issues]]. For specific errors relating to individual modules, see the Troubleshooting section of the corresponding [[Server_Modules|module's documentation page]]. |
===Hosting accounts aren't provisioned automatically=== | ===Hosting accounts aren't provisioned automatically=== | ||
| − | <html><a href="http://www.youtube.com/watch?v=Ug3wbYRpUgI" class="docs-video-tutorial"><em>Watch the video tutorial for this feature</em><span> | + | <html><a href="http://www.youtube.com/watch?v=Ug3wbYRpUgI" class="docs-video-tutorial"><em>Watch the video tutorial for this feature.</em><span> <img src="https://assets.whmcs.com/icons/youtube.png"> </span></a></html> |
| − | + | Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Logs > Activity Log''' in WHMCS 7.x and earlier) 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: | |
*[[Server Modules]] | *[[Server Modules]] | ||
| Line 12: | Line 12: | ||
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: | 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 | + | * Ensure you have a default server set in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Products/Services > Servers''' (denoted by an asterisk *) and that a server is selected on the account that you are trying to setup. |
* If a server group has been configured ensure at-least one server has been added to the group. | * If a server group has been configured ensure at-least one server has been added to the group. | ||
| − | * The module selected under | + | * The module selected under '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Products/Services > Servers''' is the same as the module selected under '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Products/Services > Products/Services > Edit > Module Settings'''. |
===Server Command Error - Curl Error - Couldn't connect to host (7)=== | ===Server Command Error - Curl Error - Couldn't connect to host (7)=== | ||
| − | 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 | + | 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 (for cPanel it would be 2086/2087, Plesk 8443, and DirectAdmin 2222). Leave these 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 administrator or hosting provider to open those ports. |
===Other Module Command/Registrar Error=== | ===Other Module Command/Registrar Error=== | ||
| Line 25: | Line 25: | ||
===Required Product Module <nowiki>''</nowiki> Missing=== | ===Required Product Module <nowiki>''</nowiki> Missing=== | ||
| − | This error message indicates that a module command was performed for a product to which no module is assigned. | + | This error message indicates that a module command was performed for a product to which no module is assigned. Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Products/Services > Products/Services > Edit > Module Settings''' 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. | 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. | ||
===Allowed memory size of xxxxx bytes exhausted=== | ===Allowed memory size of xxxxx bytes exhausted=== | ||
| − | An error message | + | An error message like "''Allowed memory size of xxxxx bytes exhausted (tried to allocate xxxx bytes)''" means that WHMCS has reached maximum amount of memory available per the <tt>memory_limit</tt> 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. |
| − | + | Take this opportunity to ensure all the other [[System Requirements]] are met. | |
===Server Command Error - Curl Error - 28 connect() timed out=== | ===Server Command Error - Curl Error - 28 connect() timed out=== | ||
| Line 45: | Line 45: | ||
* There is no firewall on your server blocking the requests from WHMCS | * There is no firewall on your server blocking the requests from WHMCS | ||
| − | * Enable | + | * Enable or disable SSL mode on your servers by going to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Products/Services > Servers > Edit'''. |
===406 Not Acceptable=== | ===406 Not Acceptable=== | ||
| − | A 406 - Not Acceptable error usually is due to the server's mod_security rules blocking the query from WHMCS being executed. | + | A ''406 - Not Acceptable'' error usually is due to the server's <tt>mod_security</tt> rules blocking the query from WHMCS being executed. |
| − | To resolve this | + | To resolve this, check the <tt>mod_security</tt> logs to see which rule is being triggered and [https://github.com/SpiderLabs/ModSecurity/wiki/ModSecurity-Frequently-Asked-Questions-%28FAQ%29#how-do-i-whitelist-an-ip-address-so-it-can-pass-through-modsecurity|whitelist that rule]. If you do not have access to the server <tt>mod_security</tt> logs or to change the rule configuration, contact your server administrator or hosting provider. |
===Server load, uptime and phpinfo always say Unavailable or 00:00:00=== | ===Server load, uptime and phpinfo always say Unavailable or 00:00:00=== | ||
| − | In order for these values to be obtained, the | + | In order for these values to be obtained, the <tt>/status/index.php</tt> file 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, | 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, | ||
{{troubleshooting}} | {{troubleshooting}} | ||
Revision as of 14:11, 4 August 2020
This page provides the explanations and solutions to general errors which may occur with multiple modules. For troubleshooting and debugging instructions, see Auto Setup Issues. For specific errors relating to individual modules, see the Troubleshooting section of the corresponding module's documentation page.
Contents
- 1 Hosting accounts aren't provisioned automatically
- 2 Server Command Error - Curl Error - Couldn't resolve host (6)
- 3 Server Command Error - Curl Error - Couldn't connect to host (7)
- 4 Other Module Command/Registrar Error
- 5 Required Product Module '' Missing
- 6 Allowed memory size of xxxxx bytes exhausted
- 7 Server Command Error - Curl Error - 28 connect() timed out
- 8 406 Not Acceptable
- 9 Server load, uptime and phpinfo always say Unavailable or 00:00:00
Hosting accounts aren't provisioned automatically
Watch the video tutorial for this feature. 
Review Configuration () > System Logs (Utilities > Logs > Activity Log in WHMCS 7.x and earlier) 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:
Server Command Error - Curl Error - Couldn't resolve host (6)
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 Configuration () > System Settings > Products/Services > Servers (denoted by an asterisk *) and that a server is selected on the account that you are trying to setup.
- If a server group has been configured ensure at-least one server has been added to the group.
- The module selected under Configuration () > System Settings > Products/Services > Servers is the same as the module selected under Configuration () > System Settings > Products/Services > Products/Services > Edit > Module Settings.
Server Command Error - Curl Error - Couldn't connect to host (7)
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 (for cPanel it would be 2086/2087, Plesk 8443, and DirectAdmin 2222). Leave these 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 administrator or hosting provider to open those ports.
Other Module Command/Registrar Error
Steps for identifying the cause of other Module Command or Registrar Command errors can be found in our Troubleshooting Guide.
Required Product Module '' Missing
This error message indicates that a module command was performed for a product to which no module is assigned. Navigate to Configuration () > System Settings > Products/Services > Products/Services > Edit > Module Settings 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.
Allowed memory size of xxxxx bytes exhausted
An error message like "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.
Take this opportunity to ensure all the other System Requirements are met.
Server Command Error - Curl Error - 28 connect() timed out
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
- 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:
- There is no firewall on your server blocking the requests from WHMCS
- Enable or disable SSL mode on your servers by going to Configuration () > System Settings > Products/Services > Servers > Edit.
406 Not Acceptable
A 406 - Not Acceptable error usually is due to the server's mod_security rules blocking the query from WHMCS being executed.
To resolve this, check the mod_security logs to see which rule is being triggered and that rule. If you do not have access to the server mod_security logs or to change the rule configuration, contact your server administrator or hosting provider.
In order for these values to be obtained, the /status/index.php file 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,