wfls_twofactor_required

  • Resolved Snerdey

    (@snerdey)


    3 years, 1 month ago

    Hello everyone,

    I’ve recently changed to LiteSpeed and added the rule to .htaccess as well as allowed the IP’s of WF to update. All is working fine except to login now I have to hide Wordfence plugin via hosting, then put it back.

    Continues to ask for 2FA, does not display the field to enter it.

    Perhaps another code fix I’m missing?

    Just started with most recent update within past 3 days or so.

    Thank you!
    Scott

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @snerdey, thanks for getting in touch.

    This is quite interesting as the main LiteSpeed setup, IP whitelisting and “noabort” changes don’t usually mess with the 2FA.

    My feelings would be either a plugin conflict that may have appeared due to a version update when the switch to LiteSpeed happened or the possibility of 2FA being carried over with a migration without being reconfigured. After hiding the Wordfence plugin to sign in, have you tried re-adding 2FA when the problem occurs?

    If you have, let me know if there are reports of specific error messages received, or red browser console error messages that may suggest a Javascript conflict. If there are, disable all plugins except for Wordfence and default back to a theme such as Twenty Twenty-One before again trying to sign in. If that works, re-enabling everything one-by-one can point to where a conflict might be occurring that could be breaking the login process.

    Thanks,

    Peter.

Viewing 1 replies (of 1 total)
  • The topic ‘wfls_twofactor_required’ is closed to new replies.

Tags