“No available Cloudflare zone”, cfut_ (53 characters)
-
Litespeed lugin not updated with the new CloudFlare cfut_ (53 characters) key format.
Please update to the new 53 characters and not the Bearer auth for keys with 40 caharacters.Cyberpanel support gave me the below explanation and its spot on:
“The issue is a compatibility problem between LiteSpeed Cache plugin’s Cloudflare integration and the API key format you’re using. The key currently saved in LiteSpeed Cache starts with
cfut_(53 characters) — this is a Cloudflare API Token, which the standalone Cloudflare plugin handles correctly using Bearer authentication.However, LiteSpeed Cache has a rigid check: it only uses Bearer auth for keys that are exactly 40 characters. Anything else, it treats as a Global API Key and sends the wrong authentication headers (X-Auth-Email + X-Auth-Key). Since your token is 53 characters, it sends it using the wrong method, Cloudflare rejects the request, and the zone lookup fails — hence “No available Cloudflare zone.”
This also explains why the standalone Cloudflare plugin works fine — it has smarter key detection (checks if the key is 37 hex chars for Global API Key, otherwise uses Bearer).”
You must be logged in to reply to this topic.