• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Default plesk-apache-badbot fail2ban doesn't work

For anyone interested; If you have supplemented your bad bots filter list, like I have, you most likely end up with thousands of banned IP's. In some cases even almost entire subnet ranges. Which you may (or may not) like to permanently ban.

For this purpose I've created a script that groups all bans from fail2ban into their respective subnets. Making it easier to see how many IP's from a subnet a currently banned. I shared the script in the Resource section of the forum, as I think this might help other users too. See: Instruction - [Fail2ban] Bash script to group multiple banned IP into subnets
 
I would also like to know what the "date pattern" is please. I've have this jail enabled on all servers and it hasn't been catching any bots (specifically GPTBot), and believe that may be the cause. I am using the stock conf/regex patterns.

Also, just for peace of mind... Will any changes be overwritten in future Plesk updates, or are these jails completely safe to modify?

[Edit]
The date pattern is:

datepattern = ^[^\[]*\[({DATE})
{^LN-BEG}

At the bottom of /filter.d/apache-badbots.conf
 
Back
Top