• Resolved gioglifx

    (@gioglifx)


    Hello,

    I’m getting a 127.0.0.1 and I’ve followed the instructions, but I can’t seem to find a solution. Would you mind helping?

    Normally, I could login with a “secret word” normally and would use my username/password + the math captcha and all would be dandy. But, when attempting to login with the url, it gives me a 127.0.0.1.

    I FTP’d into the plugins’ folder and renamed the actual plugin to something else. Of course that worked… and now I could log into my dashboard using the default WordPress …/wp-admin/

    The issue is that when I try to activate the plugin, it reverts to the error. I removed everything from the .htaccess except the default block:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    That didn’t work. It still sends me to the 127.0.0.1 if I try to activate the plugin. So, I tried to delete the .htaccess completely and press “save” under permalinks ( I didn’t change the permalinks, just pressed save ) to generate a new .htaccess. I tried to activate the plugin but still gives me the error.

    I upgraded to PHP 7.3, that didn’t do much help with the plugin.

    *****************

    Even though I completely removed the plugin for now. I can keep some of the security blocks the plugin inserted into the .htaccess to at least have some security, but I had to remove a couple to be able to login, like:

    #AIOWPS_SIX_G_BLACKLIST_END
    #AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_START
    RewriteEngine On
    RewriteCond %{REQUEST_URI} (wp-admin|wp-login)
    RewriteCond %{REQUEST_URI} !(wp-admin/admin-ajax.php)
    RewriteCond %{HTTP_COOKIE} !MyVERY_Secret_Login_URL= [NC]
    RewriteCond %{HTTP_COOKIE} !aiowps_cookie_test_8igq= [NC]
    RewriteRule .* https://127.0.0.1 [L]
    #AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_END
    #AIOWPS_BLOCK_SPAMBOTS_START

    …and now I don’t have a math captcha, and a non-default login URL. Plus, I’ll be missing out on any new updates from you guys!

    Please help if possible.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, try the following steps to completely remove the plugin and start from scratch.

    – FTP to your host and delete the plugin’s folder. Although this is normally carried out when you deactivate and delete the plugin as the website administrator.

    – FTP the .htaccess file from your site to your computer and edit and remove all the code between and including the following tags: Make sure you upload the .htaccess file back into the same location you downloaded the file from via FTP.

    # BEGIN All In One WP Security
    # END All In One WP Security

    – Log into phpMyAdmin and locate the database for the website you are working on. Look for any table entry with the following name aiowps and delete those tables. There should be 6 tables associated with this plugin, in addition to the options settings. There will also be other entries for transients and plugin version etc. The following is a list of tables and entries found in the database.

    | aiowps_events |
    | aiowps_failed_logins |
    | aiowps_global_meta |
    | aiowps_login_activity |
    | aiowps_login_lockdown |
    | aiowps_permanent_block |
    | commentmeta |
    | comments |

    -There are other aiowps settings saved in the WordPress “options” table, under the option name “aio_wp_security_configs”. You should also delete the “aio_wp_security_configs” row in the options table.

    The above steps will delete the plugin completely from your database and allow you to start from scratch.

    Let me know how you go.

    Regards

    • This reply was modified 5 years, 4 months ago by mbrsolution.
    Thread Starter gioglifx

    (@gioglifx)

    Hello,

    Thank you VERY MUCH for your kind help, that worked!

    I had deleted each and still wasn’t working, but it now it works. The reason it seems was because there were duplicate tables. They were with the previous DB Table Prefix. So, the tables were doubled. After looking into my wp-config file, I double-checked the correct prefix, and deleted the tables with the old prefixes, installed and activated the plugin – now it’s back to the beautiful plugin in its place! I love the 404 add on by the way!

    Again, thank you very much for your kind help.

    Best regards.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    I am glad to you fixed your issue ??

    Enjoy the plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error 127.0.0.1 – even after new htaccess’ is closed to new replies.