Wordpress LScache Plugin: No available Cloudflare zone issue
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi! Im having an issue with the use of Cloudflare API inside the LiteSpeed Cache plugin for WordPress. I am currently unable to purge the cache from LiteSpeed Purge All ? Cloudflare dropdown choice in the top bar menu in WordPress admin panel. I tried to query Cloudflare API directly from terminal using curl, but I cannot find any errors on the response json. Moreover, I have many sites with the same configurations as this one, and all of them are able to use successfully the Purge All ? Cloudflare LiteSpeed Cache feature. This is the only one that is causing me an issue. Just to be clear, Cloudflare API field is ON within the LiteSpeed Cache > CND > CDN Settings tab, and the Global API Key is filled, same as Email Adress and Domain , though the text input field of Domain is outlined in orange. When I go to LiteSpeed Cache > CDN > Manage tab and clic on Check status, a No available Cloudflare zone message appears on top. Is there a way to fix it? Report number: TWJXJSMY This topic was modified 1 month, 2 weeks ago by idannoiza. The page I need help with: http://treallegriragazzimorti.it please try the debug log , see what log says when you do check status I have just tried, and unfortunately, it doesnt state anything explicit to me. Here are the logs of what is happening when I click on Check Status from LiteSpeed Cache > CDN > Manage tab. I have checked LiteSpeed output in debug logs when I save the configurations for Cloudflare in LiteSpeed Cache > CDN > CDN Settings tab. I saw that Cloudflare would query this endpoint https://api.cloudflare.com/client/v4/zones?status=active&match=all&name=mypage.com and get a failure. When I tried again from curl in terminal, I did get an error and it seemed that the mail was wrong: although I share websites between accounts with different mails in Cloudflare personal space, one mail would work and the other one wouldnt. The strange thing is, the website is registered under the account with the other mail, the one that didnt work. So if anyone get around the same issue, try changing the mail, or maybe the mail and API Token combination.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference