Domain Reseller Module Update Guide
How Do You Update a Domain Name API Module? (Quick Answer)
- Download the latest module for your panel from the GitHub repository.
- Back up your existing module files.
- Upload the new files, overwriting the old ones.
- Confirm the version number in your panel's admin area.
- Run an API connection test (balance check).
- Test domain lookup, registration, and DNS operations.
Introduction
Running a domain reseller business means your panel and your registrar API need to work together flawlessly. Whether you're operating a white label domain reseller platform or scaling an existing domain reseller program, the registrar module is what connects automation panels like WHMCS, WiseCP, HostBill, Blesta, ClientExec, and FOSSBilling to the Domain Name API. Keeping it updated is critical: it's what keeps domain registration, transfers, renewals, and DNS management running without errors.
This guide goes beyond a basic update walkthrough — it also covers the errors resellers run into most often, such as a WHMCS registrar error, a failed domain registration, or a WiseCP module error, along with how the wider domain registrar API integration process works.
If you've recently migrated to the new Domain Name API platform, review the guide below before updating any modules:
Post-Migration Integration Guide
What Is a Domain Name API Module?
A registrar module is the connector that lets your automation panel — WHMCS, WiseCP, HostBill, Blesta, or ClientExec — talk to the Domain Name API. It's what powers domain registration, transfers, renewals, DNS management, and contact updates directly from your panel, without manual API calls.
Keeping the module current matters for two reasons: security and performance. On the security side, older modules sometimes rely on outdated authentication methods. On the performance side, current modules use faster, more reliable API endpoints with fewer failure points.
Why You Should Update Your Module
An outdated module can look fine on the surface while quietly accumulating risk. The most common problems include:
- Failed domain registrations and transfers
- API errors during renewal
- DNS management screens that don't behave correctly
- WHOIS data that won't stay in sync
- Authentication errors
- Incompatibility with newer PHP versions
For example, a WHMCS reseller running an outdated module might hit a 'Registrar Error' when registering a domain under a newer TLD — usually because the module doesn't yet support that TLD's parameters.
⚠️ If You've Migrated to the New Domain Name API Platform
If any of the following applies to you, review the migration guide before updating modules:
- You're using dm.domainnameapi.com
- You've generated new API keys
- You're on the new integration model
Before You Update
A few minutes of prep makes the whole process smoother:
- Back up your current module folder.
- Back up your panel's database.
- Note down your API username and password.
- Check your server's PHP version.
- Check your firewall settings and file permissions.
- Confirm your FTP or file manager access works.
Downloading the Latest Modules
All current modules are published free of charge on GitHub. Pick the repository that matches your panel:
➜ Download the Latest Modules (GitHub)
You'll find separate folders for WHMCS, WiseCP, HostBill, Blesta, ClientExec, and FOSSBilling. Click Download next to your panel, then extract the ZIP file on your computer.
Updating the WHMCS Module
To update your WHMCS domain registrar module:
- Connect to your server using an FTP client like FileZilla, or the cPanel/Plesk File Manager.
- Upload the modules folder from the downloaded package to your WHMCS root directory (usually public_html or httpdocs).
- If prompted to overwrite existing files, choose Overwrite All.
- Log in to your WHMCS admin panel.
- Go to System Settings > Domain Registrars.
- Confirm the new version number appears next to the Domain Name API module, then save your settings.
Common WHMCS Issues
If you see a 'WHMCS registrar error' or a failed domain registration after updating, make sure the module uploaded completely and that your API credentials were re-saved. Clearing the WHMCS cache sometimes resolves lingering issues too.
Updating the WiseCP Module
To avoid a WiseCP domain module error after updating:
- Connect to your server via FTP or File Manager.
- Upload the WiseCP module folder to coremany/modules/Registrars/DomainNameApi (or the matching directory for your module structure), overwriting existing files.
- Go to your WiseCP admin panel.
- Navigate to Settings > Service Settings > Domain Registrars.
- Open the Domain Name API module to confirm the version updated successfully.
Updating the HostBill Module
HostBill registrar integration files are typically uploaded to includes/registrars/, though the exact path can vary by version.
- Download the HostBill folder from the GitHub repository.
- Upload the files to includes/registrars/ (or the path specified in the GitHub README).
- In the HostBill admin panel, go to Modules > Registrar Modules.
- Enable the Domain Name API module and confirm your API credentials.
➜ Download the HostBill Module
Updating the Blesta Module
The Blesta domain registrar module is uploaded under components/modules/ or plugins/.
- Download the Blesta folder from the GitHub repository.
- Upload the files to components/modules/, overwriting the existing ones.
- In the Blesta admin panel, go to Settings > Company > Modules.
- Reconfigure and save the Domain Name API module.
Updating the ClientExec Module
ClientExec domain management module files are typically placed under registrars/.
- Download the ClientExec folder from the GitHub repository.
- Upload the files to registrars/, overwriting the existing ones.
- In the ClientExec admin panel, go to the Registrar settings.
- Select the Domain Name API module and confirm your API credentials.
➜ Download the ClientExec Module
For every panel: folder structures can shift between versions, so always check the README in the GitHub repository before uploading.
Signs of Version Mismatch
You can usually tell a module is outdated by the type of error your panel throws. The most common symptoms by platform:
WHMCS
- Registrar Error
- Invalid API Response
- Domain Registration Failed
WiseCP
- Domain Sync Failed
- Authentication Failed
HostBill
- Transfer Failed
- Balance Error
Blesta
- Contact Not Found
ClientExec
- Registrar Communication Error
If you're seeing any of these, an outdated module is the most likely cause — and the error code table below covers how to fix it.
Error Codes and How to Fix Them
Most support tickets trace back to one of the errors below. Use this table to resolve the majority of issues yourself.
| Error | Likely Cause | Affected Platform | Fix |
|---|---|---|---|
| Authentication Failed | API credentials are missing or incorrect in the module | All platforms | Re-enter your API username and password in the panel settings, then run the connection test |
| Invalid API Response | An outdated module version is incompatible with current API endpoints | WHMCS, WiseCP, HostBill | Upgrade to the latest module release from GitHub |
| Registrar Error | The module doesn't support the registrar's newer parameter structure | WHMCS, Blesta | Install the latest module and re-save the configuration |
| Contact Not Found | Contact data is stored in an outdated format | WHMCS, ClientExec | Re-run contact synchronization using the updated module |
| Transfer Failed | A required EPP code or transfer parameter is missing in the module | All platforms | Update the module and retry the transfer from the current interface |
| Domain Sync Failed | Panel database records don't match the API's records | WHMCS, WiseCP, HostBill | Restart synchronization through the updated module |
| Balance Error | The balance check function expects an older API response format | All platforms | Update the module and reload the balance screen |
| Connection Timeout | A server firewall is blocking outbound API requests | All platforms | Allow outbound access to the Domain Name API endpoints through your firewall |
| PHP Fatal Error | The module isn't compatible with the server's current PHP version | WHMCS, Blesta, ClientExec | Check your server's PHP version and update the module accordingly |
| Undefined Method | Module files were partially updated, mixing old and new versions | All platforms | Delete the old module folder entirely and reinstall the latest package |
| Missing Registrar Module | Module files weren't uploaded to the correct directory | All platforms | Check the GitHub folder structure and move the files to the correct path |
Confirming the Update Worked
After updating, run through these checks to catch any leftover issues early:
- Confirm the balance check screen loads correctly
- Run a domain availability search
- Try a test domain registration
- Test a DNS update on an existing domain
- Test a transfer in a sandbox or low-risk scenario
- Test updating contact information
Advanced Troubleshooting
If the standard steps don't resolve the issue, check these less common causes:
- PHP version compatibility: confirm your server's PHP version falls within the module's supported range
- Firewall restrictions: make sure your server can reach the Domain Name API endpoints
- SSL certificate validation issues: confirm your server's certificate chain is current
- cURL configuration problems: confirm the PHP cURL extension is enabled and up to date
- DNS resolution issues: confirm your server can resolve the API's domain correctly
- File permissions: confirm the module files are readable/writable by the panel
- API endpoint changes: very old modules may point to a retired endpoint — updating resolves this automatically
Frequently Asked Questions
Is updating the Domain Name API module mandatory?
It isn't strictly mandatory, but it's strongly recommended. Outdated modules can become incompatible with future API changes, leading to failed domain operations.
Will I lose my current settings during the update?
No. Updating module files doesn't delete your stored API credentials or domain records, since that data lives in your database, not in the module files themselves.
Should I delete the old module and reinstall, or just overwrite it?
Overwriting is usually sufficient. If there's a major structural change between versions, though, it's safer to remove the old folder entirely and install the new package cleanly.
Do I need to back anything up before updating?
Yes. Backing up both the module folder and your panel database lets you roll back quickly if something goes wrong.
Which PHP versions are supported?
Supported PHP versions vary by panel and module release. Check the README in the GitHub repository for the most current compatibility details.
How do I test the API connection after updating?
Open the module settings in your panel and run the balance check or connection test option to confirm the API is responding correctly.
I recently migrated my reseller panel to the new Domain Name API platform — what should I do?
In that case, review the Post-Migration Integration Guide before updating modules, since you'll likely need new API keys and a different integration setup.
Where do I upload the module in WHMCS?
The modules folder from the downloaded package goes into your WHMCS root directory, typically public_html or httpdocs.
Where do I upload the module in WiseCP?
Module files go into coremany/modules/Registrars/DomainNameApi, or the equivalent directory matching the module's folder structure.
What's the HostBill module folder structure?
HostBill modules are typically placed in includes/registrars/, though the exact path can vary by panel version.
How do I update the Blesta module?
Module files go into components/modules/ or plugins/, after which you confirm the configuration from the panel's admin area.
Where does the ClientExec module live?
ClientExec module files are usually placed under the registrars/ directory.
Why does domain lookup fail right after updating?
This is usually caused by an incomplete upload or API credentials that weren't re-saved. Confirm all files uploaded fully and that your API details are entered correctly.
Can I use a file manager instead of FTP?
Yes. The File Manager in cPanel or Plesk works just as well for uploading and overwriting module files.
Does updating the module take my site offline?
No, the rest of your site keeps running normally during the file upload. Only domain-related operations might be briefly affected.
I run multiple panels — do I need to update each one separately?
Yes. Each panel has its own module structure, so you'll need to download and update the matching package from GitHub for every panel you use.
The old version number still shows after updating — what now?
Clear your browser cache and reload the admin panel. If it persists, double-check the files were uploaded to the correct directory.
Which files from the GitHub repo should I skip uploading?
.gitignore, README.md, and LICENSE aren't needed on the server. It's fine to skip them, or delete them afterward if you already uploaded them.
When should I contact support after an update?
If the fixes in the error code table above don't resolve the issue, reach out to the Domain Name API support team.
As a new reseller, which module should I use?
Pick the folder matching your automation panel (WHMCS, WiseCP, HostBill, Blesta, ClientExec, or FOSSBilling) from the GitHub repository.
Will updating the module affect my existing domains?
No. The update only changes the connection files between your panel and the API — your domains, registration data, and customer records are untouched.
Will pending transfers stop working during the update?
No, transfers already in progress continue to be processed on the API side. Only starting a new transfer from the panel UI may be briefly unavailable until the module finishes uploading.
Do I need to regenerate API keys for the new panel?
Not if you're simply updating the module on your existing platform. If you've migrated to the new Domain Name API platform, though, you will need new API keys saved in the panel.
Can I still use my old cp.domainnameapi.com account?
That depends on your migration status. If your account has moved to the new platform, check the current login URL and API details in the Post-Migration Integration Guide.
How do I update the FOSSBilling module?
Same approach: download the FOSSBilling folder from GitHub, upload it to the relevant registrar modules directory, then enable the module and save your API credentials from the admin area.
Take Your Domain Automation Further
Domain Name API is a domain registrar infrastructure serving 200+ countries, supporting 40,000+ resellers, and offering an extensive TLD portfolio. With full integration support for WHMCS, WiseCP, HostBill, Blesta, and ClientExec, you can automate domain registration, transfers, and DNS management end to end.
Is Your Module Up to Date?
Download the latest release for free and update your panel with confidence:
Ready to Automate Your Domain Sales?
Automate domain registration, transfers, and renewals with Domain Name API, access an extensive TLD portfolio across 200+ countries, and take advantage of the white label reseller program.
Used by 40,000+ resellers worldwide — automate your domain sales pipeline with Domain Name API.
Conclusion
Keeping your Domain Name API module up to date is the foundation of a reliable, error-free panel. Follow the steps above to update safely, and you'll avoid the WHMCS registrar errors, failed registrations, and WiseCP module errors that send most resellers to support in the first place.
You can always find the latest modules here:
If you've moved to the new platform, review the migration guide first:
➜ Post-Migration Integration Guide
Run into anything unexpected along the way? The Domain Name API support team is happy to help.
