• entumas

    (@entumas)


    Hello
    From version 1.4.11, 2FA has stopped working correctly.
    The new version 1.4.12 is supposed to fix the bug.
    But the error persists on some of the websites where I am using this functionality.
    Does it occur to you what could be happening?
    Thanks

Viewing 12 replies - 16 through 27 (of 27 total)
  • Kat

    (@9livesillustration)

    I have the same situation, no errors that can be seen in the dev console, the debug messages or the server logs. Disabling all other plugins has no effect. Disabling this plugin I get right in.

    The only visible error message is one the front end that says :
    Error:?The username field is empty.
    Error:?The password field is empty.

    This has only happened since versions after 1.4.10. I have made no other adjustments to my log in process between updating this plugin and starting to see the error.

    Plugin Support Plamen M

    (@plamenm)

    I completely understand how frustrating it can be when you’re facing technical issues and it seems like they can’t be easily resolved through our forum discussions. To get to the bottom of this, we really need to replicate the issue on our end and delve into some detailed debugging. It’s challenging to pinpoint the exact cause with so many potential factors at play just by talking about it here.

    We’ve previously encountered some compatibility issues with our plugin when used alongside the WPS Hide Login plugin, so that’s something to be mindful of. If you’re using a custom admin URL, please ensure that it’s configured to work with our plugin, rather than through a third-party security service. Additionally, clearing your browser cookies can often help, especially before you set up the 2FA feature.

    For those of you who are SiteGround customers, I would recommend submitting a support ticket through the User Area of your SiteGround account for more personalized assistance. If you’re not with SiteGround, the best course of action I can suggest might seem a bit tedious, but it could resolve the issue. Try completely disabling and deleting the plugin, then carefully check for any residual records in the database and remove those as well. After that, reinstall and set up the most recent version of the plugin, making sure to clear all site caches and, very importantly, your browser cookies.

    Regards,
    Plamen.M
    Tech Support Team
    SiteGround.com

    Kat

    (@9livesillustration)

    The WPS Hide Login plugin provides functionality that the SiteGround security plugin does not include. Is there a solution being actively worked on to fix incompatibility with that plugin?

    There was no issue using these together in earlier versions.

    • This reply was modified 7 months ago by Kat.
    Plugin Support Plamen M

    (@plamenm)

    Thank you for the update. I know that the WPS Hide Login plugin is rather popular. However, it is coded without 2FA support. This is why, for the time being, the suggestion is to disable this plugin and use the Custom Login URL feature in our plugin, which is specially coded with 2FA integration in mind. Additionally, our security plugin is a all-in-one security solution with much more complete set of protection features. Also, it is never recommended to use more than one plugins which offer the same functionality. Keeping the number of plugins low on a WP install is one of the main recommendations for Good site administration practices.

    Regards,
    Plamen.M
    SiteGround.com

    Kat

    (@9livesillustration)

    Thank you, I am aware of best practices and keeping the number of plugins low. Unfortunately, the way the Security Optimizer plugin handles the custom login url is not acceptable to the client so in this case I’ll have to look for an alternative security solution and host for them. It would be excellent if Security Optimizer added a few more customization controls as far as the custom URLs feature in the future.

    atontchev

    (@atontchev)

    Hello!

    We have also noticed that at the moment the plugin suddenly no longer allows logins and displays a misleading error message:

    Error: Username field is empty
    Error: Password field is empty
    Restricted area, please login to continue.

    Both fields in the form are not empty and were previously filled in and validated with the corresponding 2FA code – however, after entering the code from the authenticator app, the error message appears each time and the login cannot be completed.

    Is there currently any evidence of possible incompatibilities between the plugin and the latest WordPress version?

    This is the only change to our system in a fortnight and the system behaviour of the plugin may be related to this upgrade.

    Thank you for your great support in this matter.

    Plugin Support Gergana Petrova

    (@gpetrova)

    Hello @atontchev,

    The plugin is tested up to WordPress version 6.5.2 and no functionality issues have been observed on a standard install. The issue is most likely related to an incompatibility with other plugin and/or theme.

    Please verify if the Security Optimizer is updated to it’s latest version – 1.4.13 and that there are no conflicting settings from other security plugins active at the same time. Make sure your site is also properly configured to work over https://.

    If you’re a SiteGround client – you can contact our Support team from your Client Area – in case the issue persists.

    Best Regards,
    Gergana Petrova

    atontchev

    (@atontchev)

    Hello Gergana, thanks for you kind reply. We’re testing now different technical scenarios and will try our best.

    Best regards to beautiful Sofia (BG),
    Anton

    Thread Starter entumas

    (@entumas)

    It’s not incompatibility with plugins or themes.
    I have disabled all the plugins and the problem persists.

    Plugin Support Delyan Delov

    (@delyandelov)

    Hi @entumas,

    The latest plugin release (1.4.13) should address the issue you are describing. Please make sure you have updated the plugin.

    What else you can try is to disable the 2FA via WP-CLI using the following command:
    wp sg secure 2fa disable
    and then use the reset link to set up the 2FA anew. You can do that using another administrator user if needed.

    Thread Starter entumas

    (@entumas)

    Not true @delyandelov, you can read the entire thread.

    atontchev

    (@atontchev)

    We have tried all sorts of things all day today and can confirm that none of the recommended solutions work and lead to an improvement in the situation.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘2FA don’t work’ is closed to new replies.