Support » Plugin: All In One WP Security & Firewall » Cannot log in to admin panel -Possible bug

  • Hi guys, been using your plugin for a while and only recently noticed that i cannot login to the admin panel.

    I need to FTP first, disable your plugin, then re-enable it.

    I dont have the wp-admin hidden or changed.

    Any ideas?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Same issue on two sites.

    My kind web host identified the issue for me and renamed the plugin.

    It appears I had old version. I updated the plugin but it now seems to work with the revised folder name all-in-one-wp-security-and-firewall-bak

    I assume it will be OK, but would prefer the original name, renaming file returns me to the same issue.

    Any comments from developers would be appreciated.

    ColinK

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, do you know if your IP address has been blocked? Do you see any error messages displayed when you try to log in?

    Thank you

    Hi, no ip being blocked. I have been using your plugin for about a year now and this has only happened in the past 2 months.

    Happens on all my sites i place into maintenance mode now.

    Plugin Author wpsolutions

    (@wpsolutions)

    Hi,
    You didn’t specify the error or behaviour that you see when you “cannot login to the admin panel”.

    Can you please provide more info?
    Also I encourage you to do some troubleshooting and start with some plugin/theme conflict tests.
    In addition try doing some tests to see if one of the aiowps features is somehow causing this behaviour.

    Hi there, I am having same issue.
    After disabling plugin, login as admin is possible.
    Funny thing is that everything has worked last week, and I haven’t done any updates, they are scheduled for today.
    Error we are getting is pretty generic, internal server error. Through the AIO Security setting we didn’t change admin URL, it stayed WordPress generic.
    When I try to activate again AIO Security through WordPress admin dashboard, I again get internal server error.
    It seems that cannot find redirect_to path, which from (just as example) “https://example.com/wp-login.php” should redirect to “https://example.com/wp-login.php?redirect_to=https%3A%2F%2Fexample.com%2Fwp-admin%2F&reauth=1”, but when you disable plugin it clearly sees the path.

    • This reply was modified 2 years, 7 months ago by ljiljau.
    Plugin Author wpsolutions

    (@wpsolutions)

    If you are getting “500 Internal Server Error” then it could be a number of things.

    Maybe it’s something related to your server apache config??
    See this example:
    https://stackoverflow.com/questions/21158375/htaccess-file-gives-500-internal-server-error
    You may need to do some troubleshooting and ask your host provider to help you find the reason.

    It seems that cannot find redirect_to path, which from (just as example) “https://example.com/wp-login.php” should redirect to “https://example.com/wp-login.php?redirect_to=https%3A%2F%2Fexample.com%2Fwp-admin%2F&reauth=1”, but when you disable plugin it clearly sees the path.

    I don’t quite get the connection between the activation of the aiowps and the above path. Does the “internal server error” occur immediately after aiowps activation or some other time when you are trying to login?
    If it’s when you are trying to login with a redirect, did you try removing all of the part from the URL starting from “?redirect_to…” till the end and just enter the yoursite.com/wp-login.php?

    Thanks for the answer, but it started working without me doing anything in particular.
    But first to answer to your last question.
    Yes, internal server error occurred immediately after aiowps is being activated.

    After aiowps deactivation we were able to login to admin dashboard. I tested it few more times, whenever aiowps is deactivated, login is possible. Deactivation of plugin is done through renaming it, as I have direct access to file system, we host our site on our own infrastructure, IIS and Windows Server 2012.

    After few hours of aiowps being inactive/disabled, I activated it again and planning to continue troubleshooting next day, but it started to work normally. First thing I checked this morning is logging to our WordPress site, which went completely normal.

    Just as a note, we have this plugin on our site from 2014. In the past there were some minor compatibility issues with aiowps and translate plugin, as we were using qtranslate, but it was solved very quickly.

    • This reply was modified 2 years, 7 months ago by ljiljau.

    You didn’t specify the error or behaviour that you see when you “cannot login to the admin panel”.

    Hi

    Apologies, when i put the site into maintenance mode, then log out, and want to log back in, i cannot get to the admin login screen, as the maintenance mode screen shows up.

    Plugin Author wpsolutions

    (@wpsolutions)

    i cannot get to the admin login screen

    If you type yoursite.com/wp-admin then yes you will not be allowed to get to the login page.

    However if you type your proper login URL, eg, yoursite.com/wp-login.php,
    then you should be able to access the login page.
    If you have renamed your login page then you simply need to enter the URL containing your secret slug.

    Hi,

    Having same problem.
    With aiowps activated cannot go to any other page on dashboard, get error, “This page isn’t working
    jannafabian.es is currently unable to handle this request.
    HTTP ERROR 500”
    If I rename aiowps in Cpanel, then dash is working.
    It seems that there is a conflict with Contact Form 7, if I deactivate it works okay.
    I need CF7 so what can be done?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi @goatherd999,

    It seems that there is a conflict with Contact Form 7,

    Please read the following support thread. Let me know if your issue is similar or the same.

    Thank you

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Cannot log in to admin panel -Possible bug’ is closed to new replies.