Not logging attempts with WordPress 4.0

  • Resolved tomierna

    (@tomierna)


    10 years, 4 months ago

    I recently installed wp-fail2ban on all of my WP installations, and had it working just fine. The many sites on the server were all logging to /var/log/messages (CentOS) and fail2ban was happily adding IP addresses to IPTables.

    I’ve just updated one of my most highly trafficked sites to WP 4. Immediately, logging for that installation stopped. Of course, I’m now being hit with a distributed brute-force on that install.

    Any pointers?

    https://www.ads-software.com/plugins/wp-fail2ban/

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi, my installation stopped working after upgrading to 4.0.1

    Restarting fail2ban and reactivating the plugin did not work. No messages in /var/log/auth.log And I am under attack at the moment:

    meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:51 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
    meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:52 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
    meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:52 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
    meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:53 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“

    Any clues?

    Sorry to bother, they keep trying non-existing link ()302, therefore no inlog in WP, therefore no entry in auth.log, therefore no block ??

    I will set a firewall rule myself for this fellow. Or maybe better, a rewrite rule to my actual login, so that fail2ban can help me for next cases

    Thanks for the great work!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Not logging attempts with WordPress 4.0’ is closed to new replies.