Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter stlecho

    (@stlecho)

    Rolling back to Wordfence Security v8.0.0 does not solve the problem.

    Deactivating all plugins except Wordfence Security v9.0.1 does not solve the problem.

    • This reply was modified 5 days ago by stlecho.
    Plugin Support wfmargaret

    (@wfmargaret)

    Hi @stlecho,

    Thanks for already testing the rollback and the plugin conflict test. That rules out the Wordfence version and your other plugins.

    A greyed-out Log In button with no error matches what happens when Wordfence’s reCAPTCHA is turned on, but the Site Key or Secret Key isn’t valid, for example, keys created for a different domain.

    To check this, deactivate Wordfence, log in, and then reactivate Wordfence. You’ll stay logged in. Then go to Wordfence > Login Security > Settings and see whether “Enable reCAPTCHA on the login and user registration pages” has a checkmark. If it does, remove the checkmark, save, and try logging in from a private browser window. If that works, create new v3 keys for your domain in Google’s reCAPTCHA admin console and enter them in the same section, then turn the option back on. The setup steps are here: https://www.wordfence.com/help/login-security/#recaptcha-heading

    If reCAPTCHA isn’t enabled, open your login page, press F12 to open your browser’s developer tools, and click Log In. Then send me screenshots of the Console and Network tabs. You can also email the screenshots to wftest @ wordfence . com if you prefer. Please include your forum username in the subject line so I can match it to this thread, and reply here to let me know when you’ve sent it.

    Thanks,
    Margaret

    Thread Starter stlecho

    (@stlecho)

    Updating the recaptcha keys solved the problem. Thanks a lot Margaret.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.