"An error occurred, please try again later." when trying to use "DNS Management"

[ZizDead]

Hi

 

I seem to have some trouble using the new "DNS Management" feature.

when I try to use it as a client I get the "An error occurred, please try again later."

I followed the documentation instructions and entered my ResellerClub Branded URL in Setup > Domain Registrars, I left Setup > Domain Pricing at 0 (I tried with other values as well), in ResellerClub control panel I entered the server IP and the IP of the domain where WHMCS is installed under "HTTP API"

 

Before I configured my Branded URL in "Setup > Domain Registrars" I clicked a couple of times on "DNS Management" button, a new blank screen opened, but now the new screen won't open and I get the error I mentioned.

 

I don't know what the cause, nothing show up in "System Activity Log", everything else seem to work.

[christofire]

I was getting this same error. In my case, the problem was an incorrect "BrandedURL" in the Domain Registrar Settings.

 

However, now, the DNS Management option is there and (apparently) accepts new settings, but the changes do not update on the registrar side.

 

FWIW I'm using Net Earth One (same logicboxes setup). I'm going to wait until tomorrow to see if it is a propagation issue as I just changed to NEO's DNS servers on my test domain.

[dansgalaxy]

I am currently having an error with this too.

 

It appears WHMCS isn't passing the AuthToken to NEO causing invalid credentials errors for me.

 

As URL being used is "http://domainmanager.xdnet.co.uk/servlet/ManageServiceServletForAPI?orderid=xxxxxxx&auth-token=&service-name=dns" for example.

[mikie]

I am currently having an error with this too.

 

It appears WHMCS isn't passing the AuthToken to NEO causing invalid credentials errors for me.

 

As URL being used is "http://domainmanager.xdnet.co.uk/servlet/ManageServiceServletForAPI?orderid=xxxxxxx&auth-token=&service-name=dns" for example.

 

Is there a fix for this???

[dansgalaxy]

Is there a fix for this???

 

I *think* it was that DNS management wasn't enabled for the domain on NEO side.