Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter sidro

    (@sidro)

    Hi Marko,

    Yes it happened after the 5.0.2 php-redis update. Found this fix somewhere by changing delete command to del in line 155 of Cache_Redis.php and it stops the deprecated messages on my error log. Im not sure if this really fix the issue or other effect on redis functionality

    return $accessor->del( $storage_key );
    //return $accessor->delete( $storage_key );

    • This reply was modified 6 years, 9 months ago by sidro.
    Thread Starter sidro

    (@sidro)

    im using php package from sury.org and no way to downgrade php-redis to 4.3.0, i already cleared my apt archive of previous version.

    tried switching to php7.2 same thing

    • This reply was modified 6 years, 9 months ago by sidro.
    • This reply was modified 6 years, 9 months ago by sidro.
    Thread Starter sidro

    (@sidro)

    i noticed that it only happened when the attack is persistent, ie in milliseconds apart, probably just timing issues

    2019-07-07 18:43:58,646 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:00,649 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:01,650 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:02,652 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:04,654 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:06,657 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:07,659 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:09,661 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:10,663 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:11,665 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:14,668 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:17,672 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:19,675 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    2019-07-07 18:44:20,676 fail2ban.actions[1430]: INFO    [wordpress-hard] 47.92.254.178 already banned
    Thread Starter sidro

    (@sidro)

    i used ip route for blocking instead of iptables, ip address is already blocked by ip route but somehow are able to connect on my wordpress site, other jails are working fine without the already banned messages

    :~$ ip route list | grep -i 5.188.62
    unreachable 5.188.62.5 
    :~$ ping 5.188.62.5
    connect: No route to host
    • This reply was modified 6 years, 11 months ago by sidro.
Viewing 4 replies - 1 through 4 (of 4 total)