The Google Auth Security module is licensed as a one-time purchase. The license is valid for use on one WHMCS installation only. This model delivers predictable costs for adding Google Authenticator-based two-factor authentication to WHMCS admin and client logins without ongoing subscription fees. It balances accessibility for administrators with necessary controls on distribution.

If you move your WHMCS installation to a new IP address, change the path of the WHMCS installation or change the domain name that your WHMCS installation is running under your license will need to be re-issued so that it may activate under the new location. The license is bound to these three environment variables at the time of activation. This binding is deliberate: it prevents casual duplication across unrelated servers and gives our team accurate context when diagnosing activation or runtime problems.

#Core Licensing Provisions

  • One-time purchase with lifetime use rights on the licensed system
  • Strictly limited to a single WHMCS installation
  • License key generated against the combination of server IP, install path, and primary domain
  • Automatic invalidation when any of those three values change

#Why Environment Binding Is Used

Server IP addresses, filesystem paths, and domain names serve as a low-overhead fingerprint for the licensed instance. When any of these change, the module treats the environment as a new installation. This is standard practice for commercial WHMCS addons. It stops license sharing while allowing legitimate users to migrate hardware or reorganize sites. For hosting operations that frequently provision new servers or perform domain migrations, understanding this policy up front prevents unexpected authentication lockouts after a move.

#Common Scenarios Requiring Re-Issuance

Three frequent triggers exist. First, moving WHMCS to a different server or VPS that carries a new public IP address. Second, relocating the WHMCS directory tree to a new absolute path during filesystem reorganization or version upgrades. Third, changing the primary domain name that WHMCS responds to, whether for rebranding or consolidation onto a new hostname. In each case the existing license key will fail validation on the next attempt to load the module. Plan the re-issue before you cut over traffic so that security enforcement remains continuous.

#Requesting a License Re-Issuance

Gather the original license details, the new IP address, the updated installation path, and the new domain. Submit this information to our sales team. They will validate the request against the original purchase and generate a fresh license key compatible with the current environment. The turnaround is typically short, but schedule it during a maintenance window if the module controls critical login paths. Keeping a copy of the original receipt and license email accelerates the process.

If you have any questions about the licensing of this product, please contact our sales team! They can clarify edge cases such as subdomains, load-balanced front ends, or how license reactivation interacts with WHMCS updates.

Practical takeaway: Evaluate your long-term hosting roadmap before initial activation. The one-time purchase model for the Google Auth Security module supplies reliable 2FA functionality at a fixed cost, provided you account for the re-issuance step whenever IP, path, or domain changes occur. Document your current license fingerprint alongside your WHMCS configuration so future migrations can be handled without interrupting security enforcement.