• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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