Install the current Nabtech Domain Nexus registrar connector in WHMCS

Install the current connector published in your Nabtech reseller area's Module downloads. This is a registrar connector for your own WHMCS installation. The provider's full Domain Nexus addon is a separate product and installation.

01 Prepare your account

Back up WHMCS files and database. Check the downloaded release notes against your WHMCS and PHP versions. In API Access, create the permitted email/API-key credential and save the key when it is revealed. Use the exact Username or email shown with that credential.

02 Install the generated package

  1. Copy modules/registrars/MODULE_SLUG from the ZIP into your WHMCS installation, preserving the generated folder name.
  2. For exact catalogue pricing, also copy the accompanying modules/addons/MODULE_SLUG_pricing directory.
  3. Open System Settings > Domain Registrars, activate the connector's display name and open Configure.
  4. Set API URL to https://my.nabtech.co/modules/addons/nabtechresellerdns/api/index.php.
  5. Enter Username or email and API key, then save. Do not paste an HMAC secret or bootstrap token into the API-key field.
  6. Run the connection test where offered and confirm it identifies your reseller account. Keep TLS verification enabled.

03 Assign domains and pricing

Under System Settings > Domain Pricing, assign the connector as registrar for the TLDs you intend to sell. Domain registration is configured through TLD pricing and registrar assignment; it does not require creating an ordinary hosting product for every extension.

Review your retail currency, periods and margin. Use the exact catalogue-sync guide when importing independently priced years, and avoid competing price-sync tools.

04 Test the full order journey

Check availability and an owned domain read, then verify controlled registration, transfer and renewal workflows. Keep normal WHMCS cron and domain synchronization running. Pending upstream work must remain pending until the provider confirms completion.

Do not let both the retired registrar module and the new connector submit the same order. Preserve existing operation references while migrating and inspect uncertain requests before retrying.

How do I verify the connector before enabling customer management?

Nameservers, contacts, lock, EPP, privacy, DNS and forwarding depend on the account, TLD and provider. A visible WHMCS button is not proof that the upstream feature is enabled. Test those controls on an appropriate domain.

For an update, back up and overlay the new release without renaming the module. Preserve settings, review migration notes and repeat a read-only test plus scheduled synchronization. Provide support with the connector version and redacted error references, never the API key.

  • 0 Users Found This Useful
  • domain-nexus, development
Was this answer helpful?

Related Articles

Get started with the current Nabtech Domain Nexus v2 API

The current Nabtech reseller API uses Domain Nexus v2. It provides domain ordering and...

Renew a domain through the Domain Nexus v2 API

Renew an owned domain with POST /v2/domains/{domainId}/renew. The request uses the current...

Request and retrieve a domain EPP authorisation code through the API

The current EPP workflow uses POST /v2/domains/{domainId}/epp-code to request an authorisation...

Read stored domain contact assignments through the v2 API

Use GET /v2/domains/{domainId}/contacts to read the contact assignments stored for a domain in...

Read a domain's desired nameservers through the v2 API

Use GET /v2/domains/{domainId}/nameservers to read the desired nameserver records stored for an...