• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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
 
Back
Top