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

Issue Fail2ban does not block IPs Couldn t load target

cisco

New Pleskian
Here's my error.
Plesk Onyx 17.8.11 Update #49

fail2ban.action [10650]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-apache[ \t]' -- stdout: ''
fail2ban.action [10650]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-apache[ \t]' -- stderr: ''
fail2ban.action [10650]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-apache[ \t]' -- returned 1
fail2ban.CommandAction [10650]: ERROR Invariant check failed. Trying to restore a sane environment
fail2ban.action [10650]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports http,https,7080,7081 -j f2b-apache
iptables -w -F f2b-apache
iptables -w -X f2b-apache -- stdout: ''
iptables -w -X f2b-apache -- stderr: "iptables v1.6.0: Couldn't load target `f2b-apache':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\niptables: No chain/target/match by that name.\niptables: No chain/target/match by that name.\n"
fail2ban.action [10650]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports http,https,7080,7081 -j f2b-apache
iptables -w -F f2b-apache
iptables -w -X f2b-apache -- returned 1
fail2ban.actions [10650]: ERROR Failed to execute ban jail 'plesk-apache' action 'iptables-multiport' info 'CallingMap({'ipjailmatches': <function <lambda> at 0x7fb06bd8c9b0>, 'matches': u
 
Anyway, I'd suggest you try to reinstall fail2ban first.
 
Back
Top