Open Widmo opened 2 years ago
check your api token. It usually means that your token is wrong.
I think token is ok, cause if I set domain_id it will work.
IMHO domain_id detection does not work correctly.
I think token is ok, cause if I set domain_id it will work.
IMHO domain_id detection does not work correctly.
May i know how to setuo domain_id ?
Mine somehow "pterodactyl.example.com" becomes "example.com" then "com" then nothing 0.0
Newest acme.sh
I think token is ok, cause if I set domain_id it will work. IMHO domain_id detection does not work correctly.
May i know how to setuo domain_id ?
Sorry, I mean Zone ID:
CF_Zone_ID=
Can confirm this is the case for a multi-zone setup. The zone recognized is the first one, instead of the second one, when renewing/issuing the second certificate. The zone recognized matches 1:1 the first zone, instead of the second. This is still an issue on the lastest version with --upgrade.
Found the bugger - it's not directly a bug with acme.sh, it was that there's a main config where you have a SAVED_CF_Zone_ID and additionally a config per domain, with its own CF_Zone_ID as well, which was set to the wrong value - I don't know when the configuration diverged but my screwing around manually might have been the cause.
acme.sh - latest version
Steps to reproduce: Issue wildcard certificate with CF API, usting API token only.
Debug log
Here magically domain: example.com became: com
And of course error appear.