Hi @vygon, thanks for your detailed message.
We’re currently investigating a possible link between reCAPTCHA and LiteSpeed Cache that wasn’t present until recently and only affects a handful of customers. Are you using LiteSpeed Cache at all?
If so, a good test is to disable it and see if the “CAPTCHA EXPIRED” message stops. Some customers reported success disabling object-cache.php in /wp-content/ too if you need a secondary test. You can rename it temporarily to object-cache.php.off via FTP or your host’s file manager and remove .off when you’re done testing.
Let us know how you get on,
Peter.
Thread Starter
vygon
(@vygon)
Hello,
Yes, we are using LiteSpeed Cache.
I’ve done the object-cache.php test you’ve suggested and I was able to login once I’d renamed the file. Reverting the file name also brought back the error.
Thanks for the update @vygon.
Your experience seems to reflect other feedback we’re seeing about the object caching feature in LiteSpeed Cache being the cause of the “CAPTCHA EXPIRED” message.
We think this was introduced in version 7.8.0, and 7.8.0.1 fixed an issue for failed connections, but likely didn’t fix this.
If you want to report the issue on their support forum, it may help get a resolution more quickly. Looking ourselves right now, it appears that there are other issues with transients in the object cache being reported. The fix for those forum posts will probably fix the problem with our plugin too.
Thanks again,
Peter.