• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Fail2Ban Error

M

mytoby

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.67
2025-03-06 14:00:23,548 fail2ban.transmitter [724]: ERROR Command ['status', 'sshd'] has failed. Received UnknownJailException('sshd')
2025-03-06 14:21:27,049 fail2ban.actions [724]: NOTICE [plesk-permanent-ban] Ban 195.2xx.xxx.xxx
2025-03-06 14:21:27,055 fail2ban.utils [724]: ERROR 7fbf138674b0 -- exec: iptables -w -I f2b-plesk-permanent-ban 1 -s 195.2xx.xxx.xxx -j REJECT --reject-with icmp-port-unreachable
2025-03-06 14:21:27,056 fail2ban.utils [724]: ERROR 7fbf138674b0 -- stderr: 'iptables: No chain/target/match by that name.'
2025-03-06 14:21:27,056 fail2ban.utils [724]: ERROR 7fbf138674b0 -- returned 1
2025-03-06 14:21:27,066 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- exec: for proto in $(echo 'tcp,udp' | sed 's/,/ /g'); do
iptables -w -C INPUT -p $proto -j f2b-plesk-permanent-ban
done
2025-03-06 14:21:27,066 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- stderr: "iptables v1.8.7 (nf_tables): Chain 'f2b-plesk-permanent-ban' does not exist"
2025-03-06 14:21:27,066 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- stderr: "Try `iptables -h' or 'iptables --help' for more information."
2025-03-06 14:21:27,067 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- stderr: "iptables v1.8.7 (nf_tables): Chain 'f2b-plesk-permanent-ban' does not exist"
2025-03-06 14:21:27,067 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- stderr: "Try `iptables -h' or 'iptables --help' for more information."
2025-03-06 14:21:27,067 fail2ban.utils [724]: ERROR 7fbf10e8a810 -- returned 2
2025-03-06 14:21:27,067 fail2ban.CommandAction [724]: ERROR Invariant check failed. Trying to restore a sane environment
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- exec: for proto in $(echo 'tcp,udp' | sed 's/,/ /g'); do
iptables -w -D INPUT -p $proto -j f2b-plesk-permanent-ban
done
iptables -w -F f2b-plesk-permanent-ban
iptables -w -X f2b-plesk-permanent-ban
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: "iptables v1.8.7 (nf_tables): Chain 'f2b-plesk-permanent-ban' does not exist"
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: "Try `iptables -h' or 'iptables --help' for more information."
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: "iptables v1.8.7 (nf_tables): Chain 'f2b-plesk-permanent-ban' does not exist"
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: "Try `iptables -h' or 'iptables --help' for more information."
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: 'iptables: No chain/target/match by that name.'
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- stderr: 'iptables: No chain/target/match by that name.'
2025-03-06 14:21:27,079 fail2ban.utils [724]: ERROR 7fbf13863a50 -- returned 1
 
And the jail "plesk-permanentban" has also an error (ip is making privacy - but it is the same ip):
103.1.1.1plesk-permanent-ban
103.1.1.1plesk-postfix
the first line is making manual and the second line is automatically from plesk. so it is double.
 
The root cause seems to be that some iptables chains were not added, and that might be due to either an incompatible iptables or a manually installed Fail2Ban. I suppose the easiest solution will be to remove the Fail2Ban component, then make sure it's really removed from the operating system, the reinstall it through Plesk. At least this is mostly risk-free.
 
It is a Bug, with "plesk-permanent-ban"! All Bans with this jails are still coming IN, see the Mail Log:
2025-03-08 10:33:46infopostfix/smtpd [192771]disconnect from unknown[87.120.--] ehlo=1 commands=1
2025-03-08 10:33:46infopostfix/smtpd [192771]timeout after EHLO from unknown[87.120.--]
2025-03-08 10:30:33infopostfix/anvil [192773]statistics: max cache size 3 at Mar 8 10:24:46
2025-03-08 10:30:33infopostfix/anvil [192773]statistics: max connection rate 5/60s for (smtp:87.120.--) at Mar 8 10:25:13
2025-03-08 10:28:45infopostfix/smtpd [192771]connect from unknown[87.120.--]
2025-03-08 10:28:36infopostfix/smtpd [253912]disconnect from unknown[87.120.--.--] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
2025-03-08 10:28:32infopostfix/smtpd [253912]connect from unknown[87.120.--]
2025-03-08 10:28:22infopostfix/smtpd [192771]disconnect from unknown[87.120.--] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
2025-03-08 10:28:20infopostfix/smtpd [192771]connect from unknown[87.120.--]
2025-03-08 10:28:14infopostfix/smtpd [253912]disconnect from unknown[87.120.--] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
2025-03-08 10:28:08infopostfix/smtpd [253912]connect from unknown[87.120.--]
2025-03-08 10:27:58infopostfix/smtpd [192771]disconnect from unknown[87.120.--] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
2025-03-08 10:27:55infopostfix/smtpd [192771]connect from unknown[87.120.--]
 
yes, and the reply was after the reinstall. the error is now away (at the moment). i'll watch it.
 
You must log in or register to reply here.

Similar threads

F
Issue Fail2ban error with Almalinux ¿nf_tables?
Replies
1
Views
641
Fede Marsell
F
F
Issue Fail2ban: Ip addresses are not blocked by Recidive
Replies
14
Views
1K
frg62
F
TimReeves
Fail2Ban Jail needed for /var/log/sw-cp-server/error_log
Replies
5
Views
7K
roon
R
A
Question Fail2Ban capture and ban IP, connection still being made
Replies
8
Views
2K
Bitpalast
Bitpalast
Tim_Wakeling
Issue Firewall suddenly took Plesk down overnight
2
Replies
23
Views
4K
Peter Debik
P
Back
Top