The workaround for me was disabling CloudFlare API integration in the LiteSpeed plugin – seems they messed something up there.
It is caused by a conf init progress change. When having CF, it will slow it down.
We addressed this last night, will give a patch soon.
The issue is fixed in v7.1-a5. It is on dev branch. You can try it by Toolbox -> Beta Test.
Update: the fixes are in v7.0.0.1 now on master branch. It is scheduled to release tomorrow. Pending tests now.
After installing Query Monitor on the site, I’m seeing an error message being returned from the API call to https://api.cloudflare.com/client/v4/zones “429 Too Many Requests”. It may be that the initial bug in 7.0 triggered way too many API calls that exceeded CloudFlare’s limits and is now stopping any of my sites from connecting to CloudFlare. I’m going to try updating every site to 7.0.0.1 and then see if this “420 Too Many Requests” errors will eventually go away.
That is a good point. We are pushing test progress now. Will escalate the hotfix release v7.0.0.1 to today. Appreciated for the feedback.
Good news! After updating all sites to 7.0.0.1-rc1 through the Toolbox master branch, my slowness disappeared and after about an hour the “LiteSpeed Cache CDN” settings page started functioning normally and the “429 Too Many Requests” errors stopped occuring.
@hailite It seems that LiteSpeed plugin cannot detect CloudFlare Zone. When I click the “Check Status” button, the plugin shows “No available Cloudflare zone”.
@kaiderella v7.0.0.1? After upgraded to this version, you may need to wait a while to get CF allow new API connections.
-
This reply was modified 3 months, 2 weeks ago by
Hai Zheng⚡.
@hailite Yes. I just updated and tested it.
After upgraded to this version, you may need to wait a while to get CF allow new API connections.
@hailite It’s been almost 3 hours and it still fails: https://imgur.com/a/F8z7Stw
@kaiderella I tested the CF integration(new site) and it worked for me.
Can you create a new token and remake the setup? At least refresh: Global API Key / API Token with a new one
-
This reply was modified 3 months, 2 weeks ago by
litetim. Reason: clarification
@litetim I tried it on 1 subdomain but it didn’t work.
I created a test site, with cloudflare CDN and I was not able to reproduce the issue. Didi you selected the correct access for the token?
@kaiderella please create different topic for your requests
