• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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