I’m using Caddy v2.11.2 with the dns.providers.cloudflare module. A new Cloudflare API token (user token, DNS edit + zone read) is verified as valid via /user/tokens/verify, but Caddy fails at startup with:
provision dns.providers.cloudflare: API token appears invalid
An older token (different format/length) works without issue. The failure happens before any API call (during provider provisioning), suggesting local validation may be rejecting newer token formats.
Is there any known incompatibility with newer Cloudflare API tokens?
EDIT: I see now that there are two pull requests addressing this issue.
I’m using Caddy v2.11.2 with the dns.providers.cloudflare module. A new Cloudflare API token (user token, DNS edit + zone read) is verified as valid via /user/tokens/verify, but Caddy fails at startup with:
provision dns.providers.cloudflare: API token appears invalid
An older token (different format/length) works without issue. The failure happens before any API call (during provider provisioning), suggesting local validation may be rejecting newer token formats.
Is there any known incompatibility with newer Cloudflare API tokens?
EDIT: I see now that there are two pull requests addressing this issue.