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

    (@mbrsolution)

    Hi VaultDweller you need to increase your WordPress allowed memory that is why you are seeing this error. That memory you mentioned where did you increase it from? The server or wp-config.php file?

    Thread Starter VaultDweller

    (@vaultdweller)

    > That memory you mentioned where did you increase it from?
    In .htaccess file. I created phpinfo() and checked that it is working.
    I doubt that increasing the memory could help. Anyway, what amount of memory you advise me to set?

    Could it be due to the huge amount of failed login messsages? How to clean them?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi VaultDweller in regards to your comment…..

    Could it be due to the huge amount of failed login messsages? How to clean them?

    Read the following URL and focus on Step 6.

    In regards to your comment…

    I doubt that increasing the memory could help. Anyway, what amount of memory you advise me to set?

    Some plugin or function in the backend is using up too much memory. Do you have any other security plugin or heavy resource hungry plugin installed?

    Thank you

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Hi VaultDweller,
    Can you please log into PHPMyAdmin and check the “aiowps_failed_logins” table.
    It may be that you had login lockdown enabled and you were getting hammered by login attempts from bots hence that table may be quite large.
    If so, manually delete the entries from PHPMyAdmin and see if that allows you to then display the “Failed Login Records” page.

    Are you using one of the brute force features to protect your login page?
    If not, I would advise that you do.

    Thread Starter VaultDweller

    (@vaultdweller)

    I checked the table and there were over 150K failed login records.
    Could you please implement some warning in case of large number of failed logins?

    Plugin Contributor wpsolutions

    (@wpsolutions)

    We are going to improve that feature.

    Our first improvement will be to make the logging of failed login attempts disabled by default, ie, the user will need to turn on a checkbox in order for the plugin to log these events.

    We will also make other improvements over time.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘No data on screnn in tab Failed login attempts, error in log’ is closed to new replies.