• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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