WordPress.org

Ready to get started?Download WordPress

Forums

Limit Login Attempts
No logs generated (7 posts)

  1. LFGabel
    Member
    Posted 2 years ago #

    I have the "Log IP" setting on, yet it does not show any logs. Am I doing something wrong?

  2. johanee
    Member
    Plugin Author

    Posted 2 years ago #

    Only new lockouts are logged (not failed attempts). Unless there are new lockouts nothing will be shown.

    Have the lockout statistics increased since you turned on the logging?

  3. LFGabel
    Member
    Posted 2 years ago #

    Perhaps not. Would resetting the total and active lockouts activate the logging? I'll try it and get back to you.

    Thanks for the hint.

    All the best,
    Lee

  4. LFGabel
    Member
    Posted 2 years ago #

    5 hours after resetting, I get this:

    Total lockouts: 1 lockout since last reset
    Active lockouts: 1 IP is currently blocked from trying to log in

    Should there be log information now? If there should be, it's not showing up.

    I'll try removing and reinstalling the plugin.

  5. johanee
    Member
    Plugin Author

    Posted 2 years ago #

    Interesting. Yes there should be a log, I'll take a look at it.

  6. LFGabel
    Member
    Posted 2 years ago #

    17 hours after resetting, I get this:

    Total lockouts: 4 lockouts since last reset
    Active lockouts: 2 IP is currently blocked from trying to log in

    I dug into the "wp_options" table and it does show the IPs that were logged in the option variable "limit_login_lockouts", but does not add the IPs to the option variable "limit_login_logged". When I visit the settings page for the plugin, the logged IPs do not show up at the bottom like in your supplied "screenshot-3.gif". This is expected since in your code, the log is displayed only if "limit_login_logged" has information stored in it, and it doesn't, but should it if there's data in the option variable "limit_login_lockouts"?

  7. johanee
    Member
    Plugin Author

    Posted 2 years ago #

    This issue is (finaly) fixed in 1.6.2 that was just released.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic