Hi @mb00
Thanks you for reporting this. Can you share a bit more in detail what you were doing, please? It would help us if you could answer these questions:
- Were you installing the pluigin for the fist time, or was this an upgrade?
- What version of WordPress are you using?
- What version of PHP are you running for your WordPress site?
I’m sure we’ll have more questions, but let’s start with these 🙂
Thread Starter
mb00
(@mb00)
- I’m not 100% sure, I’ve tried it couple years ago, but I don’t remember which site I’ve tried it on.
- 6.8.2
- 8.3
It manage to login with email and global token, I checked using the testing site from your official docs, and was constantly getting cf-cache-status: DYNAMIC. I’ve googled, and I saw suggestion to switch APO in Cloudflare dashboard.
At some point I tried to see plugin settings page again and then I would just keep getting the same error no matter how many times I would reload. It was ~30 mins probably before I’ve noticed after I first configured it.
Manage to login
Into your Cloudflare account inside your WordPress site?
tried to see plugin settings page again and then I would just keep getting the same error
Can you take a screenshot of what that looks like here, please?
Thread Starter
mb00
(@mb00)
https://postimg.cc/gallery/XybzKyb
Reactivated plugin, did “Sign in here”, logged in. Tried to enable APO but it was keep switching itself off after page reload, after some time the page crashed (1st and 2nd screenshots)
Thank you for that. First off, it’s unrelated, but you should update WordPress to the lastest version as soon as possible as 6.8.3 is a security release.
Can you confirm the issue is still present with just the Cloudflare APO plugin active? I want to make sure this is not some kind of conflict. More on how to debug WordPress here.
Thread Starter
mb00
(@mb00)
Unfortunately I won’t be able to test it with just Cloudflare enabled as it is a production site, but I can try to test older versions as long as they don’t break the site. I will try to troubleshoot this myself next week and see where the problem could be.
Thanks for prompt replies.
Do let us know what you find. Our fist suspicion is that it’s related to WooCommerce. Are you running the latest version of that?