• Resolved Oleg Chuvakin

    (@olegchuvakin)


    Hello, IniLerm!

    Is 404 error blocking not working?

    It seems your plugin isn’t blocking IP addresses for 404 errors. The plugin log says “Blocked” (highlighted in red), but in reality, the IP is NOT BLOCKED.

    Examples: 52.1.250.135 – 35 attacks with 404 errors; 141.255.162.234 – 63 attacks with 404 errors; 185.87.121.29 – 32 attacks with 404 errors. All three IP addresses were not blocked. Security Log reports: 2026-08-20 21:27:43 Blocked: 4320 min 52.1.250.135 Ashburn, United States (US). But searching for a blocked IP yields this result: “52.1.250.135. No IPs found for the current filter.” The results for 141.255.162.234 and 185.87.121.29 are similar: these IPs are not blocked.

    In the “404 Error Blocking” section of your plugin, I have the following blocking settings: Single IP: Block Threshold: 6; 404 Time Window (min): 18; 404 Duration (min): 4320.

    Perhaps I’m doing something wrong. Please help me.

    Oleg.

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

    (@inilerm)

    Hi Oleg,

    Thank you very much for taking the time to report this issue in detail and for your patience. We have thoroughly investigated the case and successfully identified and fixed the bug affecting the threshold blocking system (404/403/Login).

    We will be releasing update 8.12.2 within the next 24 to 48 hours (possibly sooner), which includes this fix. With this update, the blocking system will work perfectly and be much more robust.

    We greatly appreciate your help. Thanks to reports like yours, we can keep improving the plugin for everyone!

    Best regards, The Advanced IP Blocker Team

    Thread Starter Oleg Chuvakin

    (@olegchuvakin)

    Hi, IniLerm!

    Thank you! I’ll be waiting. I’m sure you’ll succeed, and your plugin will become even better.

    Thread Starter Oleg Chuvakin

    (@olegchuvakin)

    I’ve installed the updated version of the plugin (8.12.2). I’ll keep an eye on it!

    Thread Starter Oleg Chuvakin

    (@olegchuvakin)

    Hi, IniLerm!

    Thank you for your work. Attackers are now being punished for 404 errors! Here’s one example:

    IP: 91.92.34.102 → Block Type: 404 Error → Since: 2026-08-21 21:28:07 MSK → Duration: 4320 minutes → Details: Generated 6 404 errors. Triggering URL: /wp-content/plugins/gamipress/readme.txt → Location: Frankfurt am Main, Germany (DE) → Status: Blocked.

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

You must be logged in to reply to this topic.