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

WHASOLS can automatically provision services, you can specify whether this happens before or after payment, 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 > Products/Services.

  • If the auto-setup is not occurring, begin your troubleshooting by watching this video tutorial.
If that doesn't help, review Logs > System Activity 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:

Hosting accounts aren't provisioned automatically

Review Logs > System Activity Logs at the time of account creation for any error messages.

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 at the Servers tab while editing a product group at Configuration  > Products/Services:

  • You have set the correct servers and that, if using a server group, Configuration > Servers  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
  • CentOs Control Panel (CWP) - 2031 and 2030
Leave these ports open for inbound and outbound connections on the WHASOLS server and the remote server. For assistance, contact your hosting provider or system administrator.

Required Product Module '' Missing
This error message indicates that a module command was performed for a product without an assigned module. Go to the Module Settings tab for a product at Configuration  > Products/Services  to check the module setting.

If the module selection has intentionally been left at None, consider using the Auto Release module. This module lets WHASOLS 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)" indicates that WHASOLS 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 WHASOLS.
  • The server doesn't exist.
In order to resolve this, make certain that:

  • Your firewalls aren't blocking requests from WHASOLS.
  • You have correctly configured SSL mode for the server at Configuration > Servers.
406 Not Acceptable
A 406 - Not Acceptable error usually is due to the server's mod_security rules blocking the query from WHASOLS.

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.

Domain Provisioning Problems
WHASOLS 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  > 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 Activity 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.

You can troubleshoot this using the steps above. If those steps do not resolve the issue, see the additional steps in Email Sending Issues.

Other Module Command/Registrar Error
For steps to identify other module command or registrar command errors, see Troubleshooting Guide.