Suggestion / request for reducing wp_IPBLC_login_failed size

  • Resolved NoNewWars

    (@nonewwars)


    9 years, 4 months ago

    My database size grows quite quickly because of the records in wp_IPBLC_login_failed being quite large for these hacking attempts that use system.multicall. It is growing at about 20MB per week.

    These records use the full 65535 characters of the variables field.

    I have recently started trimming these records so that they are only 1024 bytes long like this:

    UPDATE	wp_IPBLC_login_failed
SET	variables = CONCAT( left(variables,1017), "  etc…" )
WHERE	length(variables) > 1024

    Is there any benefit to wp_IPBLC_login_failed.variables being 65,535 bytes long? Would a shorter field be good enough?

    https://www.ads-software.com/plugins/ip-blacklist-cloud/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Adiie9

    (@ad33lx)

    Hi,
    You should keep an eye on failed login everyday and once you have blacklisted, clear table.
    variables are in TEXT field type so that complete details can be shown.

    Regards,
    Adeel

    Thread Starter NoNewWars

    (@nonewwars)

    I find it useful to leave the Failed Login Attempts list in place because of the many IP addresses that do one hack login attempt per day.

    Plugin Author Adiie9

    (@ad33lx)

    Hi,

    If you keep them there then for sure they will eat up your space.
    Try to optimize tables by using WP Clean Up plugin.

    Regards,
    Adeel

    I am struggling with this as well. It seems to me that the plugin should “Autoblock” any IP that does a Multicall login attempt.

    Ad33lx, does this seem reasonable? Are there any legitimate uses of this process?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Suggestion / request for reducing wp_IPBLC_login_failed size’ is closed to new replies.