-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report bugs to easyDNS dns api #2647
Comments
@wurzelpanzer |
@Neilpang will have a look into it tomorrow. |
Still does not work.
It shows 'invalid domain' while the domain should be registered as new. |
Could you please upload the debug log with --debug 2 enabled? |
I was trying to run for a wildcard certificate. Now it succeeded partially.
resulted in with 'invalid domain' error:
But when I did |
I am seeing a lot of these 420 Enhance Your Calm responses from rest.easydns.net too, including when using cURL on the command line.
If I want to try taking the message literally, what can we do to slow down the request rate, by a lot? |
Im gonna ask easydns about rates and limits. |
I got to suspect that 420 Enhance Your Calm might be misleading because the first test GET I made to rest.easydns.net after getting my keys got that result. In other words, it gave me a rate limit error message before my API requests even had a rate. |
@wurzelpanzer I confirmed that the 420 Enhance Your Calm responses are misleading. This is the response also for auth failure. I checked my account.conf file and saw that the SAVED_EASYDNS_Key and _Token values were reversed (my error when copy-pasting the env var yesterday). So I swapped them and the cert issue completed successfully. Woot! But with incorrect Key and Token values I got 420 Enhance Your Calm responses. So I'll write this large for anyone else who might need to know 420 Enhance Your Calm response from rest.easydns.com does NOT mean you hit a server rate limit |
I've just tried this for the first time and stumbled. With the help of EasyDNS, we realized that it was basically an authentication failure. Initially at least, EasyDNS gives you sandbox access only, and those credentials fail since the acme.sh script talks to the production environment, not the sandbox environment. Even with In addition, like @tom-- I also reversed |
Report issues with easyDNS API here.
The text was updated successfully, but these errors were encountered: