The supplied 1.0.7-rc8 package declares PHP 8.1 through 8.4. Its installation guide specifies WHMCS 8.13.1 or later within the 8.13 line, or 9.0.6 or later within the 9.0 line, with MySQL 8 or MariaDB 10.6 or later. Use a maintained WHMCS patch release that also meets WHMCS and ionCube requirements. Do not interpret the module's PHP range as permission to run a PHP version unsupported by your WHMCS release.

Check PHP extensions json, openssl, pdo, mbstring, simplexml, zip, bcmath, intl, curl, pdo_mysql and sodium. The command-line PHP used by cron needs the required extensions as well as the web PHP runtime. Use HTTPS for WHMCS and reachable, certificate-valid provider endpoints.

1. Back up the WHMCS database and files. Keep the backup outside the public web directory and confirm that you can restore it.
2. Extract the release into the WHMCS root, preserving its directories. The addon belongs under modules/addons/nabtechresellerdns. Supplied server modules include modules/servers/nabtechresellerproduct and modules/servers/nabtechpremiumdns.
3. Run the supplied secrets initialisation command as the account that owns WHMCS, using the matching command-line PHP. Choose a persistent directory outside the WHMCS and public web roots.

php modules/addons/nabtechresellerdns/bin/console secrets:init --secrets-dir=/home/ACCOUNT/.nabtech-domain-reseller

Replace the example account path with your real protected location. Record where the encryption and connector-signing keys are stored, restrict access and include them in encrypted backups. Never place these keys in a support ticket or public repository.

4. Activate Nabtech Domain Nexus under WHMCS addon modules and grant access to the intended administrator roles.
5. Complete licence configuration if your purchased edition requests a licence key. Open the addon and review its initial readiness checks.
6. Confirm that the WHMCS cron runs every five minutes and that module jobs progress. Configure providers and one test package before enabling broad product or TLD automation.

Check a provider connection, create a controlled test zone, change a harmless record and verify the job and authoritative result. Test the client-area entry with a customer who owns the test service. Administrator access alone does not prove customer entitlements are correct.

If activation fails, preserve the error and check runtime requirements, filesystem ownership, key-directory access and database privileges. Avoid repeatedly deactivating the module. The addon has a destructive data-removal option intended for deliberate uninstall, not routine troubleshooting.

• Upgrade Domain Nexus while preserving keys, settings and customer data
• Activate a purchased Domain Nexus licence and diagnose validation problems
• Keep Domain Nexus jobs, scheduled DNS changes and reconciliation running
• Add a DNS provider connection and prove that it can manage zones

• WHMCS system requirements