Account API tokens still fail with "Invalid API Token (1000)" — release needed for PR #195

[caitlin-green-sp]

Account API tokens still fail with Invalid API Token (1000) when used with the cloudflare-exporter, even though the token works with the Cloudflare API when verified directly.
Environment
Cloudflare: Account API token (verified via /accounts/{account_id}/tokens/verify)
Exporter image: ghcr.io/lablabs/cloudflare_exporter:latest (also tried 0.2.3)
CF_ACCOUNTS: Set to the account ID

Issue #158 documented that account tokens fail validation.
PR #195 (merged Feb 5, 2026) adds support for account-scoped API tokens.

Questions
Release: When will a release include the account token support from PR #195?
Docker image: Is the latest image built from master and does it include PR #195?
Workaround: Is there a supported way to use account API tokens with the current release?

Thank you!

[aymanbagabas]

I'm getting the same issue with 0.2.3 and latest. Is there a workaround until this gets tagged in a release?

[binaryoverload]

For some reason the image name changed from cloudflare_exporter to cloudflare-exporter (underscore replaced with hyphen) (In this commit cfef7bc)

When using ghcr.io/lablabs/cloudflare-exporter:latest - it works!

[heytrav]

If I try to pull that image I get an error:

docker pull ghcr.io/lablabs/cloudflare-exporter:0.2.3

Error response from daemon: Get "https://ghcr.io/v2/": denied: denied
Error response from daemon: Head "https://ghcr.io/v2/lablabs/cloudflare-exporter/manifests/0.2.3": denied: denied

same happens with tag :latest.

[binaryoverload]

@heytrav that looks like you've got an expired token for ghcr.io - try running docker logout ghcr.io and then pull the image

[heytrav]

@heytrav that looks like you've got an expired token for ghcr.io - try running docker logout ghcr.io and then pull the image

yep that was the problem, thanks!