Same issue here. Is seems that Wordfence doesn’t support reCAPTCHA if your reCAPTCHA keys have been migrated to Google’s cloud platform.
I’m now using the plugin Simple CAPTCHA Alternative with Cloudflare Turnstile for CAPTCHA protection but hopefully WordFence will replace the broken Google integration with a Cloudflare Turnstile integration.
-
This reply was modified 2 weeks, 5 days ago by
james4311.
i also have Simple CAPTCHA Alternative with Cloudflare Turnstile for CAPTCHA just for jetpack form as i was getting lots of spams..should i enable for login etc and remove the option from worfence?
Hi @koullis, thanks for getting in touch.
Do you have LiteSpeed cache installed? If so, it’s worth checking if reCAPTCHA works normally when disabling LiteSpeed Cache temporarily. There are a lot of settings, so it may be one of those causing the issue, as historically Wordfence’s features have worked with that installed.
If LiteSpeed cache does seem to be related to the issue, we’d recommend disabling JS Combine External and Inline and Load JS Deferred if they are enabled. They are on LiteSpeed Cache > Page Optimization > JS Settings (tab).
If not, it may be worth us looking into the Google Cloud reCAPTCHA keys suggestion above if that seems to have a positive effect when you try it, although I believe we are running a number of test sites (without this issue) that have had their keys migrated over to Google Cloud’s interface already.
Many thanks,
Peter.
hi
yes i have litespeed cache. from a fast check those 2 options are disabled so ill check tomorrow if i disable it entirely if i still get problem
Fantastic, thank-you @koullis. Our QA team will be happy to look into the cause further if you can confirm that disabling LiteSpeed Cache seems to solve the problem.
Peter.
@wfpeter I looked into this further and actually there was a mismatch between my reCAPTCHA site key in Wordfence’s settings and the reCAPTCHA ID in Google Cloud Platform – my own fault when migrating reCAPTCHA to GCP several weeks ago. After correcting the key in Wordfence and purging both LiteSpeed’s cache (which I also use) and Cloudflare’s cache, then Wordfence is working again with reCAPTCHA enabled.
That’s great news, I’ll await @koullis looking into theirs too.
Peter.
thank you for your replies. my keys are correctly with new GCP..in the mean time litespeed plugin had an update as well these days.. as i faced the problem after pc/firefox restart i really dont want to do one right now maybe over the weekend.did clear cache though of site and i also checked with different browsers and logged in fine.
-
This reply was modified 2 weeks, 2 days ago by
koullis.
Thanks for letting us know @koullis, we’ll keep the topic open should we need to investigate further after the restart.
Peter.
We’re seeing additional feedback from our customers that the object caching feature in LiteSpeed Cache is the cause of the “CAPTCHA EXPIRED” message. Renaming /wp-content/object-cache.php to object-cache.php.off temporarily seems to confirm it.
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, 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,
Peter.
