Plugin doesn’t work anymore with version 2.6

  • Resolved acsnaterse

    (@acsnaterse)


    10 months, 2 weeks ago

    After upgrading to version 2.6.x the 2FA method via email keeps asking for a new code, and keeps sending a new code. With the result that you can’t login. Also the usage of a backup code does not help.

    Strangely enough, this is not the case for every user, and also does not happen in Chrome Incognito. However in “regular” Chrome and Firefox we experience this issue. Even after deleting all cookies, it does not work in the “regular” browser.

    A rollback to 2.5 “fixes” the issue.

Viewing 1 replies (of 1 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello there!

    Thank you for reaching us today! I am really sorry to hear about this experience with the plugin.

    I would have a few more questions so that we can get a better understanding of the potential causes for this:

    1. It was mentioned that this issue is intermittent, and it’s happening even after clearing cookies on the browser – what about caches? Can you confirm if caches have also been cleared up? on browser and site level.

    1. Have you tried by any chance to remove and reinstall the plugin from scratch? This will ensure a clean installation, but the plugin will need to be set up once again, same for users.

      If you want to try this, and see if the issue persists, simply head to Settings – Delete data upon uninstall then proceed with plugin removal/reinstallation. (this can narrow down the possibility of a corrupted/bad migration process of the plugin)
    2. Does this happen on a regular log in using default WordPress form? Or, does this happen while trying to log in via a Custom log in form/page?
    3. What about trying to perform a login test with caching / security plugins disabled while using a default WordPress theme temporarily instead of a custom one? Does it make any difference?
    4. Can you offer us a breakdown of the tests performed while on different browsers (regular browsing not incognito) – can you spot a pattern maybe with a specific browser on which the log in does not work as expected?

    Would be nice to try as well – Microsoft Edge, Firefox, Opera, Safari → since each browser has it’s own caching / cookie system, which works a bit different and may offer us some clues, and details to try to reproduce this ourselves somehow.

    1. Have you tried other 2FA methods (TOTP – code via generator app) for example, and noticed if the same happens?
    2. In regards to “backup codes does not help” statement – can you let us know what happens when trying to use backup code to login? Is there any error or message displayed? Can you describe the behavior of the page when backup code is used to log in?

      Looking forward to hearing back from you with as many details as possible. We really appreciate your patience and cooperation on this.

      Many thanks!
Viewing 1 replies (of 1 total)
  • The topic ‘Plugin doesn’t work anymore with version 2.6’ is closed to new replies.