• Resolved pcde

    (@pcde)


    Hi there —

    First, I love your plugin. Thank you! It has worked flawlessly for many years and many versions.

    That said, following the update to v5.0.8 I can no longer log in to my website. I have been using the Cookie-Based Brute Force Login Prevention feature and Rename the Login Page without issue for years. Now when I log in it returns a white page. I did activate some of the new 6G Blacklist features on v5.0.8 so I don’t know if perhaps that is playing a part.

    Anyways, I tried reverting to v5.0.7, tried disabling other plugins, etc etc with no change. So for now I have deactivated the AIOWPS plugin and am able to log in. But for now I am keeping my website in maintenance mode while I lack the security your plugin provides.

    I know others have reported similar problems following this update already and that you are working on a fix, but thought I would also post my problem here in case I can provide some additional or different information that might help you find the fix.

    Thanks! Looking forward to the next update.

    • This topic was modified 2 years, 1 month ago by pcde.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Prashant Baldha

    (@pmbaldha)

    It looks like you are using the Apache server and you have enabled the login whitelisting from Admin Dashboard > WP Security > Brute Force > Login Whitelist (tab) in the past. The login whitelisting feature was not working in the older AIOS version on such configured Apache servers. Starting from AIOS 5.0.8, it started working suddenly. You are trying a non-whitelisted IP address client, so you can’t browse the login screen and face the 403 error on it.

    Solution: Please add the below code line in the wp-config.php file before /* Add any custom values between this line and the “stop editing” line. */:

    
    define('AIOS_DISABLE_LOGIN_WHITELIST', true);
    

    It will disable login whitelisting on your site.

    Thanks a lot for reaching out to us.

    Thread Starter pcde

    (@pcde)

    That did the trick. Thank you!!

    Question: With the Whitelist now disabled via my wp-config.php, the actual AIOS Whitelist settings page shows the Whitelist on/off toggle checkbox is checked/on, but there is a “Whitelist has been disabled via wp-config.php” message at the top of the page. I am fine with that as everything is now working, but…

    1) Whenever the next AIOS update comes out should I remove the Whitelist instruction we’ve added to the wp-config.php file?

    2) Regarding putting myself on the Whitelist, with my Internet Host I have a dynamic IP. Is there a way to whitelist myself with a dynamic IP? Or is the Whitelist only for people with a static IP?

    Thanks so much again for your help and for the great plugin. Cheers.

    I was having the same issue, and it turns out that disabling the whitelisting option in the plugin resolved the problem. If the whitelisting option was checked, it was causing anyone with a non-whitelisted IP address an inability to login. They would just get a white screen. Disabling the whitelisting option allowed me to use the new update.

    Obviously, something in the update is interfering with the ability to use the “whitelisting” option in your plugin.

    Plugin Contributor Prashant Baldha

    (@pmbaldha)

    From AIOS 5.0.9, we have auto-disabled login whitelisting and shown a notice related to it on the admin dashboard..

    The login whitelisting was not working in previous AIOS versions older than 5.0.8 version in all non-apache servers and a few wrongly configured apache servers even if it is enabled. From AIOS 5.0.8, the login whitelisting started working suddenly.

    The login whitelisting means a few configured IP addresses can only access the login screen. Previously it was not working so many users enabled it and leave as it is because it was not working.

    Thank you for reaching out to us.

    We are glad that the issue has been resolved at your end. ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Can’t log-in after 5.0.8 update’ is closed to new replies.