Invalid WHMCS License Error After Moving to a New Server: How to Fix It

Updated: 8 October 2026 · Applies to: self-hosted WHMCS 9.0 and 8.13 LTS (from WHMCS documentation); configuration check tested with PHP 8.3

A WHMCS licence is only valid for the domain, IP address and directory it was issued for. After you move WHMCS to a new server, the Admin Area login shows License Invalid until the licence is reissued for the new location. Reissue it in the WHMCS Member Area (Services › My Licenses, select the key, click Reissue), or ask your hosting provider if the licence came with your hosting, then open the WHMCS Admin Area again on the new server.

Step 1: make sure the right key is in configuration.php

According to WHMCS, this error also appears when the key itself is wrong, so check that first. The key is in configuration.php in the WHMCS root directory:

$license = "YOUR-LICENCE-KEY";

1. Compare the value with the key shown in the WHMCS Member Area under Services › My Licenses, or with the key your hosting provider gave you.
2. Look for hidden spaces, line breaks or extra quotation marks, which WHMCS lists as a cause. A copy and paste can add a trailing space that you will not see in an editor. These commands show it (run them in the WHMCS directory):

   grep -n 'license' configuration.php | cat -A
   php -r 'include "configuration.php"; var_dump($license);'

   In our test, a key with a trailing space showed up like this (example key):

   2:$license = "WHMCS-EXAMPLE-KEY ";$
   string(18) "WHMCS-EXAMPLE-KEY "

   After removing the space, var_dump printed string(17) "WHMCS-EXAMPLE-KEY". cat -A marks each line end with $; a ^M before it means the file has Windows line endings.

Step 2: reissue the licence for the new server

• Licence bought from WHMCS: log in to the WHMCS Member Area, go to Services › My Licenses, select the licence key and click Reissue (older WHMCS help pages call the button Reissue License). According to WHMCS, the next time you visit your installation, its new location is saved as the valid location for that licence.
• Licence from a hosting provider: only the provider can reissue it, so open a ticket with them. WHMCS states that keys obtained through a hosting provider are valid only with that host: if you move WHMCS to a different provider, you need a new licence key.

Then open the Admin Area on the new server. If the error page is still shown, use its Click here to enter a new license key. link if you received a new key.

Step 3: force a fresh licence check

WHMCS keeps a local licence key and, according to WHMCS, contacts its licensing server once every seven days to confirm the location. Once you can log in, go to Help › License Information and click Force License Update for an immediate check. The same page lists the key, the valid domains and directories, and lets you Change License Key. If you cannot reach the Admin Area at all, WHMCS asks you to contact WHMCS Support.

Your clients are not locked out meanwhile: WHMCS states that the Client Area stays online even with an invalid or expired licence; only the Admin Area is blocked.

If you see "No Connection" instead

A new server sometimes cannot reach the WHMCS licensing server at all, because of DNS, cURL or a firewall. WHMCS has a built-in test: open /admin/login.php?conntest=1 on your WHMCS address (use your own folder name if you renamed admin). According to WHMCS, a working connection ends with Response Code: 200 and Connection Successful!. If it fails, check that the server resolves whmcs.com correctly and that outgoing HTTPS is allowed in the firewall.

Common reasons the error comes back

• You open WHMCS on a different domain from the one it is licensed for, for example a temporary hostname or the server IP while DNS is still changing. Use the final domain and wait until DNS points to the new server; WHMCS asks you to let DNS changes propagate fully before you reissue.
• WHMCS sits in a different directory on the new server (for example /billing instead of /clients). The directory is part of the licence, so reissue after the final move, not before.
• You reissued while the old server was still answering for the domain. Because the location is saved on the next visit after a reissue, the old server may have been registered again. Reissue once more after DNS has switched.

The rest of the move checklist

WHMCS's own move guide also asks you to:

1. Disable the cron job on the old server before you copy anything, then back up the database.
2. Update the database details in configuration.php, plus any absolute paths such as $attachments_dir, $downloads_dir, $templates_compiledir or $crons_dir.
3. Update the System URL at Configuration › System Settings › General Settings.
4. Set up the cron job on the new server, pointing to crons/cron.php.
5. Check payment gateway callbacks, email forwarders and any sign-in or gateway redirect URIs. PayPal may report IPN failures after a move (see IPN handshake invalid in WHMCS).
6. Delete the WHMCS files from the old location.

Also check that the new server meets the WHMCS 9.0 requirements (PHP 8.2 or 8.3 with a matching ionCube Loader). If your own IP gets blocked after repeated login attempts, see unblock your IP address from WHMCS. If you would rather have our engineers move WHMCS and its server for you, see server management services.

Official documentation: Invalid License Errors · Move WHMCS to a New Server · License Information