Download the Blesta package from the releases published to your reseller account. Back up Blesta and its module configuration. Check the package's compatibility requirements and test the release on an appropriate staging installation before accepting production domain orders.

For HMAC authentication, use a permitted application key from the API Clients/Keys workflow. These are different fields from the standard email/API-key option. Select the authentication method issued for this installation. If we issued a bootstrap token, use it only through the supported one-time exchange.

1. Copy the generated components/modules/MODULE_SLUG directory into Blesta, keeping its name unchanged.
2. Open Settings > Company > Modules, install the connector and add an account.
3. Set the final HTTPS endpoint. For Nabtech, use https://my.nabtech.co/modules/addons/nabtechresellerdns/api/index.php.
4. Enter the API username/email and API key, or leave email authentication unselected and use the supported advanced bootstrap or explicit HMAC fields. Click Test and save account.
5. Check authentication from both web requests and the scheduled processing environment, including any permitted source-address restrictions.
6. Configure Domain Manager's TLD assignment and yearly pricing separately from the connection details.

Check availability and read an owned domain, then verify a controlled registration, transfer and renewal. Queued provider work is not final completion. Inspect the upstream operation, allow the worker to finish and retry the same invoice or order through its supported workflow. A new invoice can represent a new purchase rather than a safe retry.

Review the service's Domain management tab. It can offer domain-scoped nameserver, contact, lock, privacy, DNS and forwarding controls when the account and upstream provider permit them. Protected records and approval rules still apply.

A saved email forwarder may need destination verification, and forwarding needs a working DNS and runtime arrangement. Do not describe a saved rule as live until its status and a real test agree. Local billing cancellation does not itself delete the registry domain.

For an email alias, check the recipient verification state and the deployed route, then send a test from another mailbox. For a website redirect, test the source hostname over HTTPS and inspect the actual destination after deployment.

Back up encrypted module settings before replacing connector files. Preserve the generated module name, review migration notes and recheck cron synchronization. If a signing key is exposed, rotate it upstream, update the module account and verify a read request. Share redacted error references rather than credentials or customer identity documents.

• Get started with the current Nabtech Domain Nexus v2 API
• Sign Domain Nexus v2 API requests with HMAC authentication
• Install the current Nabtech Domain Nexus connector in HostBill
• Install the Nabtech Domain Nexus registrar adapter in FOSSBilling