Closed jsjcjsjc closed 1 year ago
Hey @jsjcjsjc,
The error message you noticed is coming from WHMCS Core. A common error message not giving you a hint why the DNS Update failed. I can confirm that our registrar module is forwarding the exact error message to WHMCS, but WHMCS is just showing that common error message. A design issue of WHMCS imho. An improvement for this is in work on our end as such basic things should be better covered by WHMCS. The exact error message of that dns update can be identified in the Module Log. We are working on an entire improvement of that section. What you notice here is how Team WHMCS has designed the dns management which isn't customer-friendly nor is it making the dns management a success.
if you need further help with that dns update, please follow-up. hopefully the error message in module log is helping you already.
Hey @jsjcjsjc,
The error message you noticed is coming from WHMCS Core. A common error message not giving you a hint why the DNS Update failed. I can confirm that our registrar module if forwarding the exact error message to WHMCS, but WHMCS is just showing that common error message. A design issue of WHMCS imho. An improvement for this is in work on our end as such basic things should be better covered by WHMCS. The exact error message of that dns update can be identified in the Module Log. We are working on an entire improvement of that section. What you notice here is how Team WHMCS has designed the dns management which isn't customer-friendly nor is it making the dns management a success.
if you need further help with that dns update, please follow-up. hopefully the error message in module log is helping you already.
thanks, after close "TestMode", it ok now
May I ask if Blesta is better than WHMCS in this regard?
Kind regards, Frazer
On Thu, 24 Aug 2023 at 14:38, Kai Schwarz @.***> wrote:
Hey @jsjcjsjc https://github.com/jsjcjsjc,
The error message you noticed is coming from WHMCS Core. A common error message not giving you a hint why the DNS Update failed. I can confirm that our registrar module if forwarding the exact error message to WHMCS, but WHMCS is just showing that common error message. A design issue of WHMCS imho. An improvement for this is in work on our end as such basic things should be better covered by WHMCS. The exact error message of that dns update can be identified in the Module Log. We are working on an entire improvement of that section. What you notice here is how Team WHMCS has designed the dns management which isn't customer-friendly nor is it making the dns management a success.
if you need further help with that dns update, please follow-up. hopefully the error message in module log is helping you already.
— Reply to this email directly, view it on GitHub https://github.com/centralnicgroup-opensource/rtldev-middleware-whmcs/issues/260#issuecomment-1691695190, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQD5ELXMUGB4Q2HNEMWSG3XW5KMFANCNFSM6AAAAAA33PD5YQ . You are receiving this because you are subscribed to this thread.Message ID: <centralnicgroup-opensource/rtldev-middleware-whmcs/issues/260/1691695190@ github.com>
Cheers, Frazer!
Our integration with Blesta is very basic and even though I've been asking for it, it is not getting some priority atm. Especially when it comes to Domain Addons - id protection, email forwarding, dns management - the module isn't if I recall correctly supporting that. My honest opinion on Blesta: it is far behind an easy to understand UI (compared to WHMCS). HostBill is definitely a better choice if you want to continue without big hussle. I heard good things from customers switching from WHMCS to HostBill. Blesta made a big improvement step with their Domain Manager (v5) already. That's my personal experience with Blesta: While it was easy to me starting with WHMCS, I struggled with Blesta (regarding setting it up, but also covering developments).
Hope that helps.
For rounding this up: With our recent bundle version the exact API error message is now getting shown in the DNS Management section to ensure it is visible to the client. You'll have to apply template changes to make this happen.
More details available in the release notes of v21.0.0. Check the "BREAKING CHANGES".
WHMCS 8.13 RRPproxyv19.1.3 in DNS managmant,error message below