Facebook
Twitter
-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
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.
Issue Default plesk-apache-badbot fail2ban doesn't work
- Thread starter John41
- Start date
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
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
Similar threads
