• 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.

How can I add a action to fail2ban - iptables-ipset-proto

Hi OverWolf,

sorry... but I can't follow you, as it is unclear right now, WHAT is causing WHICH error/issues/problem. Pls. consider to document with a step-by-step guide, how people willing to help you may reproduce the error/issue/problem, that you currently experience.
 
Using:
[own-badbot]
enabled = true
action = iptables-ipset-proto4[name=own-badbot, port="http,https,7080,7081"]
iptables-ipset-proto6-allports[name=own-badbot, port="http,https,7080,7081"]
iptables-ipset-proto6[name=own-badbot, port="http,https,7080,7081"]
logpath = /var/www/vhosts/system/*/logs/*access*log
/var/log/httpd/*access_log
filter = apache-badbots
findtime = 43200
bantime = 604800
maxretry = 3​
without ".conf" for the action - that works for me (Plesk 17.8.11)

I think, that 's, what OverWolf found too
 
Back
Top