wp-admin redirects to 127.0.0.1

Hi,

Please accept my apologies for your inconvenience.

You might have enabled the cookie-based brute force prevention Admin Dashboard > WP Security > Brute Force > Cookie Based Brute Force Protection as indicated in the screenshot https://nimb.ws/Wmih07 in the past.

Before the AIOS 5.0.0 release, the rename login page and the cookie-based brute force prevention didn’t work at the same time. As soon as you upgraded the AIOs plugin, the cookie-based brute force prevention functionality started working, and it caused the issue for you.

Resolution:

1. If you remember the secret word, please browse the URL example.com?=secretword=1 and you will be redirected to the admin login screen.

2. If you don’t remember the secret word, then open the database from PHPMyAdmin, select the options table and search for the aio_wp_security_configs option name, copy the option_value field, paste it on https://www.unserialize.com/ and unserialize it. You should find the aiowps_brute_force_secret_word string and find the value of it, and do as described above.

3. Easy solution: In the AIOS 5.0.4 release, we have given a feature that you can disable the brute force login prevention by adding the below code line in the wp-config.php file:

define( 'AIOS_DISABLE_COOKIE_BRUTE_FORCE_PREVENTION', true );

And then try to browse the login page.

We hope you understand it. We are very sorry again.

Thank you for reaching out to us.

• This reply was modified 2 years, 5 months ago by Prashant Baldha. Reason: extra quotes from answer removed

I tried these suggestions and still getting the same redirect issue. Can someone help assist me on this issue?

bump – same for me. no solutions stated above seem to work.

added the line to wp-config,

Deleted AIOS plugin and removed all DB tables, reinstalled plugin, etc.

As soon as the plugin is activated, we get locked out of wp-admin to 127.0.0.1

• This reply was modified 2 years, 3 months ago by stealthkinetics. Reason: subscribed to reply notifications

The settings.php edit in the uploads folder described here: https://www.ads-software.com/support/topic/message-127-0-0-0-1/
fixed the issue for us. (had at least 4 sites with this issue).

No wonder uninstalling the app and zapping the database tables had no effect on the lockout issue…. grr