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

Plesk 12.5 - Fail2ban not working

Nick Sternly

New Pleskian
I've upgraded from 12.x to 12.5 and I noticed Fail2ban isn't properly working. When I took a look at the log file i'm getting a few error messages regarding missing files?

2015-09-21 07:15:51,987 fail2ban.action [31802]: ERROR iptables -n -L INPUT | grep -q 'f2b-plesk-proftpd[ \t]' -- stdout: ''
2015-09-21 07:15:51,988 fail2ban.action [31802]: ERROR iptables -n -L INPUT | grep -q 'f2b-plesk-proftpd[ \t]' -- stderr: ''
2015-09-21 07:15:51,988 fail2ban.action [31802]: ERROR iptables -n -L INPUT | grep -q 'f2b-plesk-proftpd[ \t]' -- returned 1
2015-09-21 07:15:51,988 fail2ban.CommandAction [31802]: ERROR Invariant check failed. Trying to restore a sane environment
2015-09-21 07:15:52,091 fail2ban.action [31802]: ERROR iptables -D INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j f2b-plesk-proftpd
iptables -F f2b-plesk-proftpd
iptables -X f2b-plesk-proftpd -- stdout: ''
2015-09-21 07:15:52,091 fail2ban.action [31802]: ERROR iptables -D INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j f2b-plesk-proftpd
iptables -F f2b-plesk-proftpd
iptables -X f2b-plesk-proftpd -- stderr: "iptables v1.4.21: Couldn't load target `f2b-plesk-proftpd':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"
2015-09-21 07:15:52,091 fail2ban.action [31802]: ERROR iptables -D INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j f2b-plesk-proftpd
iptables -F f2b-plesk-proftpd
iptables -X f2b-plesk-proftpd -- returned 1




This is the first time trying to use Fail2ban so I'm not sure if it's ever been working.

Currently on a CentOS 7 64bit system which is a dedicated plesk server.

Any ideas?
 
Enabling the firewall on plesk after turning on fail2ban seemed to disable it. iptables --list did not show iptables entries for the list in fail2ban.
Switched off fail2ban then switch on
iptables --list now shows fail2ban entries.
Don't know if it will last. I am on a new centos 7-64bit with 12.5.30 update #8 at 1and1
 
Subsequent fail2ban listings ARE showing up in iptables -L. So the off then on seemed to work. Have not tested survival after restart.
 
I have the same problem, Everything looks like it is working until you examine the logs. Stop and start fail2ban and iptables -L shows the chains with blocks. Has anyone found a solution to this?
 
Back
Top