License Troubleshooting - Revision history

SarahK: /* Curl Error: Connection refused - Code 7 */

2021-10-15T18:46:48Z

‎Curl Error: Connection refused - Code 7

PeterB: /* License Invalid */

2020-02-18T13:44:30Z

‎License Invalid

John: /* Specific Errors */

2019-10-29T15:51:15Z

‎Specific Errors

ChrisD: Added "WHMCS-" to the list of license key prefixes

2018-05-25T09:48:05Z

Added "WHMCS-" to the list of license key prefixes

John: /* Required function is not available */

2018-02-23T16:28:08Z

‎Required function is not available

NickH at 22:36, 22 February 2018

2018-02-22T22:36:44Z

NickH: /* Required function is not available */

2018-02-22T16:33:33Z

‎Required function is not available

NickH at 23:41, 21 February 2018

2018-02-21T23:41:34Z

NickH at 23:31, 21 February 2018

2018-02-21T23:31:52Z

NickH at 23:24, 21 February 2018

2018-02-21T23:24:44Z

@@ Line 51: / Line 51: @@
 ===Curl Error: Connection refused - Code 7===
-See [[Curl Error: Couldn't connect to host (7)|Curl Error: Couldn't connect to host]]
+See above.
 ===Curl Error: Problem with the SSL CA cert (path? access rights?) - 77===

@@ Line 8: / Line 8: @@
 *The IP address your install is located on has changed
 *The directory you are using has changed<br />
-Following any changes to the location of your WHMCS installation, the licence must be updated accordingly. Please refer to [[Licensing#Moving_WHMCS|Moving WHMCS]] for instructions on doing so.
+Following any changes to the location of your WHMCS installation, the license must be updated accordingly. Please refer to [[Licensing#Moving_WHMCS|Moving WHMCS]] for instructions on doing so.
 ==Specific Errors==

@@ Line 49: / Line 49: @@
 ===Curl Error: Couldn't connect to host (7)===
 A CURL code 7 error indicates an inability to connect to the WHMCS licensing server. This is typically caused by a firewall configuration. CURL uses port 443 for secure connections, so ensure that connections are permitted on this port.
 ===Curl Error: Problem with the SSL CA cert (path? access rights?) - 77===

@@ Line 4: / Line 4: @@
 A Licence Invalid error on the admin login page can be caused by one of the following changes:
 *The license key has been entered incorrectly<br/>
-Please ensure the full key is entered, this includes the prefix eg. "Leased-", "Owned-", "WebHost-" and "Dev-".
+Please ensure the full key is entered, this includes the prefix eg. "Leased-", "Owned-", "WebHost-", "WHMCS-" and "Dev-".
 *The domain being used to access your install has changed
 *The IP address your install is located on has changed

@@ Line 29: / Line 29: @@
 *curl_close
-All of these functions must be installed and enabled on your server in order to properly validate your license. You can check to see if these functions are available on your server or listed in the "disabled_functions" of your PHP settings. You can check this by creating a PHP Info page, as described in the [http://php.net/manual/en/function.phpinfo.php#refsect1-function.phpinfo-examples  PHP Documentation].
+All of these functions must be installed and enabled on your server in order to properly validate your license. You can check to see if these functions are available on your server by:
 The following links might be helpful in accomplishing this on your server:

@@ Line 1: / Line 1: @@
-If you are encountering a licensing error when accessing your WHMCS installation's administration area, this could indicate that the license needs updating or a server configuration issue is preventing a connection to our license server. This page details the most common errors and provides some suggested resolutions.
+If you are encountering a licensing error when accessing your WHMCS installation's administration area, this could indicate that your server is unable to communicate with our license server. This page details the most common errors and provides some suggested resolutions.
 ==License Invalid==
@@ Line 29: / Line 29: @@
 *curl_close
-All of these functions must be installed and enabled on your server in order to properly validate your license. You can check to see if these functions are available on your server or disabled in your settings by creating and checking a PHP Info page, as described in the [http://php.net/manual/en/function.phpinfo.php#refsect1-function.phpinfo-examples  PHP Documentation].
+All of these functions must be installed and enabled on your server in order to properly validate your license. You can check to see if these functions are available on your server or listed in the "disabled_functions" of your PHP settings. You can check this by creating a PHP Info page, as described in the [http://php.net/manual/en/function.phpinfo.php#refsect1-function.phpinfo-examples  PHP Documentation].
 The following links might be helpful in accomplishing this on your server:

@@ Line 9: / Line 9: @@
 *The directory you are using has changed<br />
 Following any changes to the location of your WHMCS installation, the licence must be updated accordingly. Please refer to [[Licensing#Moving_WHMCS|Moving WHMCS]] for instructions on doing so.
 ==Specific Errors==
@@ Line 19: / Line 14: @@
 This error indicates that your server has the required ''base64_decode'' function disabled in your PHP configuration. Please adjust your website's PHP configuration so as to enable the ''base64_decode'' function.
-It may be necessary for the function to be added at the server level, in which could contacting your server admin/hosting provider may be required:
+It may be necessary for the function to be added at the server level. The following links might be helpful in accomplishing this on your server:
 * https://documentation.cpanel.net/display/EA4/EasyApache+4+Home
 * https://docs.plesk.com/en-US/onyx/administrator-guide/web-hosting/php-management.70668/
 ===Required function is not available===
@@ Line 32: / Line 29: @@
 *curl_close
-All of these functions must be installed and enabled on your server in order to properly validate your license:
+All of these functions must be installed and enabled on your server in order to properly validate your license.
 * https://curl.haxx.se/docs/install.html
-You may need to reach out to your web host or systems administrator to resolve this.
+If you need further assistance, you may need to reach out to your web host or systems administrator to resolve this.
 ===Curl Error: Couldn't resolve host (6)===
-A CURL code 6 error indicates an inability for your DNS to resolve the WHMCS licensing server. This could indicate a temporary issue with your DNS provider, or a longer-term misconfiguration.
+A CURL code 6 error indicates an inability for your DNS to resolve the WHMCS licensing server. This could indicate a temporary issue with your DNS provider, or a larger misconfiguration.
 If these points have been eliminated, check your Zone files for the presence of an entry for whmcs.com and remove it if found.
@@ Line 52: / Line 52: @@
 See [[License Troubleshooting#Outdated Root CA Bundles|Outdated Root CA Bundles]]
-====Outdated Root CA Bundles====
+===Outdated Root CA Bundles===
-The license validation is made via an SSL connection. This helps to ensure the security and integrity of your license.
+The license validation is performed via an SSL connection. This helps to ensure the security and integrity of license checks.
 Errors can occur when placing the CURL call using the "curlopt_ssl_verifypeer" function if your server does not have the appropriate root certificate authority (CA) bundles to validate the SSL connection to our licensing server. This can be caused by the CA bundle files being missing or outdated.
@@ Line 61: / Line 61: @@
 Frequently updated CA Root Certificates are available from your Operating System's repository or the cURL website at https://curl.haxx.se/docs/caextract.html
-If you are unsure how to check for these certificates or update them, it is best to contact your web host or systems administrator for assistance.
+If you are unsure how to check for these certificates or update them, we recommend that you contact your web host or systems administrator for assistance.
 ===Other Curl Error Codes===
 Other CURL error codes are detailed in the official documentation at https://curl.haxx.se/libcurl/c/libcurl-errors.html

@@ Line 18: / Line 18: @@
 To test the connection between your server and the WHMCS licence server, a built-in test tool is available on the admin area login page:
- /admin/login.php?conntest=1
+/admin/login.php?conntest=1
 For example, if your admin area is located at http://yourdomain.com/admin/login.php, you'd visit http://yourdomain.com/admin/login.php?conntest=1
 A successful test result looks like:
- Testing Connection to 'https://licensing28.whmcs.com/license/test.php'...
+Testing Connection to 'https://licensing28.whmcs.com/license/test.php'...
- URL resolves to 184.94.192.12 ... Ok
+URL resolves to 184.94.192.12 ... Ok
- Response Code: 200
+Response Code: 200
- Connection Successful!
+Connection Successful!
 or
- Testing Connection to 'https://licensing28.whmcs.com/license/test.php'...
+Testing Connection to 'https://licensing28.whmcs.com/license/test.php'...
- URL resolves to 208.74.124.169 ... Ok
+URL resolves to 208.74.124.169 ... Ok
- Response Code: 200
+Response Code: 200
- Connection Successful!
+Connection Successful!
 If you see any errors, it will be necessary to work with your server admin/hosting provider to resolve the cURL connectivity issue. Showing the test results should assist in their troubleshooting.
@@ Line 75: / Line 75: @@
 ===Curl Error: Problem with the SSL CA cert (path? access rights?) - 77===
-See [[License Troubleshooting#Outdated Root CA Bundles]]
+See [[License Troubleshooting#Outdated Root CA Bundles|Outdated Root CA Bundles]]
 ===Curl Error: error setting certificate verify locations===
-See [[License Troubleshooting#Outdated Root CA Bundles]]
+See [[License Troubleshooting#Outdated Root CA Bundles|Outdated Root CA Bundles]]
 ====Outdated Root CA Bundles====