-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Open
Description
Hi. Debugging ClouDNS (maybe other hosters too) could be facilitated by actually logging the actual HTTP response instead of a generic
Invalid CLOUDNS_AUTH_ID or CLOUDNS_AUTH_PASSWORD. Please check your login credentials.
Full output with --debug
:
[Fri Sep 19 02:35:38 UTC 2025] Adding TXT value: 7UWDjlJMU4cPzjX_6BcyMSkYQzk072RYfJ4-FhrH620 for domain: _acme-challenge.evil-farmer.cloud-ip.cc
[Fri Sep 19 02:35:38 UTC 2025] Using cloudns
[Fri Sep 19 02:35:38 UTC 2025] CLOUDNS_AUTH_ID='<id>'
[Fri Sep 19 02:35:38 UTC 2025] CLOUDNS_SUB_AUTH_ID
[Fri Sep 19 02:35:38 UTC 2025] CLOUDNS_AUTH_PASSWORD='<password>'
[Fri Sep 19 02:35:38 UTC 2025] GET
[Fri Sep 19 02:35:38 UTC 2025] url='https://api.cloudns.net/dns/login.json?auth-id=<id>&auth-password=<password>'
[Fri Sep 19 02:35:38 UTC 2025] timeout=
[Fri Sep 19 02:35:38 UTC 2025] Http already initialized.
[Fri Sep 19 02:35:38 UTC 2025] _CURL='curl --silent --dump-header /acme.sh/http.header -L --trace-ascii /tmp/tmp.1XgPxwvyjP -g '
[Fri Sep 19 02:35:38 UTC 2025] ret='0'
[Fri Sep 19 02:35:38 UTC 2025] response='{"status":"Failed","statusDescription":"You don't have access to the HTTP API. Check your plan."}'
[Fri Sep 19 02:35:38 UTC 2025] Invalid CLOUDNS_AUTH_ID or CLOUDNS_AUTH_PASSWORD. Please check your login credentials.
[Fri Sep 19 02:35:38 UTC 2025] Error adding TXT record to domain: _acme-challenge.evil-farmer.cloud-ip.cc
So, clearly, the default Invalid Credentials
output is misleading:
response='{"status":"Failed","statusDescription":"You don't have access to the HTTP API. Check your plan."}'
Metadata
Metadata
Assignees
Labels
No labels