Troubleshooting
Common issues when connecting Cloudflare analytics to Henneth, and how to fix them.
Invalid API token
Henneth shows “Invalid token” or “Authentication failed” when you click Test Connection.
- The token was revoked or deleted in Cloudflare
- The token was miscopied (missing characters or extra whitespace)
- The token has expired (if you set a TTL)
Go to Cloudflare → My Profile → API Tokens, verify the token status is “Active.” If not, create a new token following the integration guide. When pasting into Henneth, make sure there are no extra spaces before or after the token string.
No data appearing
Connection shows as successful but your Henneth dashboard is empty.
- The token doesn’t have Analytics:Read permission
- The Zone ID doesn’t match the zone the token is scoped to
- Your domain hasn’t received enough traffic yet for Cloudflare to have analytics data
- Initial data import can take up to 24 hours
First, wait 24 hours after connecting — initial data import takes time. If still empty, verify in Cloudflare that your token has Zone > Analytics > Read permission and that the Zone ID you entered matches the domain the token is scoped to.
Wrong zone / zone mismatch
Data appears but doesn’t match what you expect, or you see “Zone not found.”
- The Zone ID you entered belongs to a different domain than the one the token is scoped to
- You have multiple domains on Cloudflare and copied the wrong Zone ID
Go to Cloudflare, select the correct domain, and copy the Zone ID from the Overview page sidebar. Make sure the token’s Zone Resources are set to “Include → Specific zone → [same domain].” Update the Zone ID in your Henneth dashboard and click Test Connection again.
Permission denied
Henneth shows “Insufficient permissions” or “Forbidden” error.
- The token is missing the Analytics:Read permission
- The token was created with a different permission (e.g., DNS:Read instead of Analytics:Read)
In Cloudflare → My Profile → API Tokens, click the three-dot menu on your token and select “Edit.” Verify the permission is set to Zone > Analytics > Read. If you can’t edit it, create a new token with the correct permission.
Token expired
Connection was working but stopped. Henneth shows a token error.
- You set a TTL (expiration) on the token when creating it
- Someone revoked the token in Cloudflare
Create a new token in Cloudflare with the same Zone > Analytics > Read permission. Update the API Token field in your Henneth dashboard and click Test Connection to verify.
Still having issues? Contact us at [email protected] and we'll help you get set up.