Order Form Issues
There was an error in your request
When checking a domain availability this indicates that your firewall is blocking the whois port 43. Please ensure port 43 is open. It could also indicate your server is unable to connect to the whois server listed in the /resources/domains/whois.json file - ensure your server is able to connect to the whois server on port 43 for the TLD listed in this file.
There was a problem connecting to the domain registry
When checking a domain availability this indicates that your firewall is blocking the whois port 43. Please ensure port 43 is open. It could also indicate your server is unable to connect to the whois server listed in the /resources/domains/whois.json file - ensure your server is able to connect to the whois server on port 43 for the TLD listed in this file.
Domain Checker reports domains available when they are registered
The cause of this problem is the same as the above two points, a connection problem with the whois server. Begin by reviewing Logs for any error messages beginning with WHOIS Lookup Error at the time of performing the domain availability check. Some potential errors are explained below:
Extension not listed in /resources/domains/whois.json.
WHASOLS can check the availability of over 900+ domain extensions as standard. Unfortunately, the domain you are looking up is not amongst them. However, this can be added by modifying the /resources/domains/whois.json file and entering the WHOIS server details for the desired TLD.
Further information is published here.
Error: 110 - Connection Error
This error indicates that your firewall is blocking the whois port 43. Please ensure port 43 is open. It could also indicate your server is unable to connect to the whois server listed in the /resources/domains/whois.json file - ensure your server is able to connect to the whois server on port 43 for the TLD listed in this file.
Error: 0 - php_network_getaddresses: getaddrinfo failed: Name or service not known
This indicates that an entry does exist in the /resources/domains/whois.json file for the TLD in question or your server is unable to resolve it.
Double-check with the IANA database that you're connecting to the correct whois server, and if not it can be added or changed by following these instructions. If the entry for the TLD in question does exist, speak to your server admin to investigate why you server is unable to resolve it.
Invalid TLD/Registration Period Supplied for Domain Registration
This error indicates an order has been placed for a TLD or registration period that hasn't been configured.
An order cannot be created because no products or domain registration items have been selected
this error indicates an order has been placed for a TLD or registration period that hasn't been configured.
Order form not displaying domain results
This problem manifests itself as follows, during the product ordering price after selecting the "Use an existing domain and change the nameservers" option and clicking "Go", no results are returned.
This problem is caused by Cloudflare script minification/Rocketloader features. This causes Cloudflare to replace the javascripts WHASOLS uses to check the availability with their own copies. Cloudflare's javascripts do not contain the necessary code.
Please disable RocketLoader and script minification options in your Cloudflare control panel if you face above mention error.
Free domains do not show as free on product configuration step
When configuring an order, the domain will show as full price until the checkout page. This is because the discount is reliant upon the client selecting the appropriate TLD, product and billing cycle, so cannot be applied until both the domain and product are in the cart with the billing cycle selected so WHASOLS knows that they're eligible to receive the free domain.
Product price displays a smaller amount on the cart than configured
This is caused by the Monthly Pricing Breakdown feature.
If you do not wish prices displayed in this way, disable it in the Ordering tab at Configuration > General Settings.
Product is configured as prorata but no pro-rating is occurring
You have ticked the "Prorata" option in a product's Pricing tab with in the admin area, but upon ordering the price is not being pro-rated.
Solution: This is caused by the Signup Anniversary Prorata feature, which overrides the product prorata setting. If you'd rather products be pro-rated to a specific date rather than the client's signup date, disable it in the Ordering tab at Configuration > General Settings.