• Resolved Phil Emery

    (@noise)


    Been using Wordfence for years without issue.

    In the last month or so we’re getting errors on all wordfence sites with recaptcha issues. Sometimes its the “CAPTCHA EXPIRED: The CAPTCHA verification for this login attempt has expired. Please try again.” or other times it’s recaptcha timing out with an error saying the site key is missing.

    I know there has been an update to recaptcha but not sure if this is related.

    We’ve had to uninstall wordfence from all the sites to get them working

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Phil Emery

    (@noise)

    Google has changed Recaptcha quite a bit. Instead of a simple and powerful solution, they’ve made it unnecessarily complex and old keys need to be upgraded.

    Considering these sites have been working fine for years, there is a change and WF needs to be aware of it of find some way of dealing with it.

    We’re seeing the same issue of “CAPTCHA EXPIRED: The CAPTCHA verification for this login attempt has expired. Please try again.” We had to turn off reCAPTCHA under ‘Login Security’ as a result. However, we use Divi and also have reCAPTCHA V3 setup on form fills and they work just fine. It seems to me that the issue is related to how WordFence works with reCAPTCHA. Hopefully WF will have an update in the near future that resolves this issue.

    Thread Starter Phil Emery

    (@noise)

    PLEASE stop deleting other users who have the same problem.

    It’s a real douche move and it makes you look really bad (people will wonder what you’re trying to hide)

    Come on, Wordfence – you’re better than that.

    Moderator Support Moderator

    (@moderator)

    PLEASE stop deleting other users who have the same problem.

    It’s not Wordfence doing that. They cannot.

    When someone piles on to a topic and it is found this is the reply they get.

    If you need support then per the forum guidelines please start your own topic.

    https://www.ads-software.com/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

    Don’t pile onto other people’s topics unless you are going to help the original person. Writing “Same issue here, what the heck WORDFENCE!” is not that.

    The other user was asked to start their own topic which they did.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @noise, thanks for getting in touch.

    We are currently looking into the possibility that some customers may have been affected by recent changes to reCAPTCHA, although the quantity of cases in comparison to customers using our Login Security features is relatively small. There could be caching, or other factors on your server that are specifically affecting your experience so getting a diagnostic report would be helpful to us.

    Visit the?Wordfence > Tools > Diagnostics?page to send the output to us at?wftest @ wordfence . com. Click on?“Send Report by Email”. Please add your forum username where indicated and?respond here after you have sent it.

    NOTE:?It should look as follows – Screenshot of?Tools > Diagnostic > Send by Email

    Many thanks,
    Peter.

    Thread Starter Phil Emery

    (@noise)

    the problem is that we can’t even log into the site because of Wordfence. The only way to log in is to completely delete the plugin and remove the code from the files.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @noise,

    As with 2FA issues, renaming the /wp-content/plugins/wordfence plugin folder to “wordfence_bak” (without quotes) should let you access and log into your site normally. You can then rename the folder back to “wordfence” to send a diagnostic as the login page’s reCAPTCHA is effectively bypassed for that session.

    I’m getting ahead of seeing your diagnostic to confirm its presence, but seeing “site key missing” is possibly linked to a LiteSpeed Cache issue. They have a feature that was affecting the Google URLs. After disabling the “Localize Resources” option on the “Localization” tab of the LiteSpeed cache settings, we also had to click “Purge All – CSS/JS Cache” on the LiteSpeed plugin’s Toolbox page.

    Thanks again,
    Peter.

    • This reply was modified 3 weeks, 1 day ago by wfpeter.
Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.