Namecheap API key not working
-
@girish Sent. Just to let you know (its in the email) but I changed my main domain to the domain I was able to add as a test, but now I get the same error when trying to change my main domain back to lahijiapps.dev.
I suspect this has quite a bit to do with my IP changing when we got a new router.
-
@atrilahiji What I found is that the curl call fails most of the time but works now and then.
<?xml version="1.0" encoding="utf-8" ?> <ApiResponse Status="ERROR"> <Errors> <Error Number="500000">Too many requests</Error> </Errors> <Server/> <GMTTimeDifference/> <ExecutionTime>0</ExecutionTime> </ApiResponse>
Searching for above I see https://whmcs.community/topic/303288-namecheap-domain-sync-error-too-many-requests/ and https://github.com/adamdecaf/terraform-provider-namecheap/issues/9
-
@atrilahiji So, if I am "patient" and put the key one by one in your domains it does work. For example, I succeeded updating the key for the first domain as well.
-
@atrilahiji Yes, correct. The DNS calls are failing . I think as a first step, change the keys to the new key (just give 10 mins between updating each domain, it seems to work). After you have switched them over, then change the dashboard domain. It should work.
Also, per https://www.namecheap.com/support/knowledgebase/article.aspx/9739/63/api--faq#z, it seems
"Our general API calls restriction is 20/min, 700/hour and 8000/day across the whole key."
I don't think we make 20 per min, maybe something on their side is enforcing limits wrongly?
-
This can be resolved. Thanks for the help @girish!
-
@atrilahiji said in Namecheap API key not working:
@girish Lol they just said "fuck it" and doubled my quota. Testing it out.
Classic namecheap support
-
@brutalbirdie Yeah, I tried their Ghost hosting once, until I found how far behind their version updating lagged, which led me to discover Cloudron