Facebook
Twitter
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
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
