Error on logs:
2023-02-08 19:38:24,663 fail2ban.utils [49680]: INFO HINT on 127: "Command not found". Make sure that all commands in 'iptables -w -N f2b-sshd\niptables -w -A f2b-sshd -j RETURN\niptables -w -I INPUT -p tcp -m multiport --dports ssh -j f2b-sshd' are in the PATH of fail2ban-server process (grep -a PATH= /proc/pidof -x fail2ban-server/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" in another shell session and observe if additional informative error messages appear in the terminals.
2023-02-08 19:38:24,663 fail2ban.actions [49680]: ERROR Failed to execute ban jail 'sshd' action 'iptables-multiport' info 'ActionInfo({'ip': '183.99.143.30', 'family': 'inet4', 'fid': at 0x7f1151a88790>, 'raw-ticket': at 0x7f1151a88e50>})': Error starting action Jail('sshd')/iptables-multiport: 'Script error'
Error on logs:
2023-02-08 19:38:24,663 fail2ban.utils [49680]: INFO HINT on 127: "Command not found". Make sure that all commands in 'iptables -w -N f2b-sshd\niptables -w -A f2b-sshd -j RETURN\niptables -w -I INPUT -p tcp -m multiport --dports ssh -j f2b-sshd' are in the PATH of fail2ban-server process (grep -a PATH= /proc/
pidof -x fail2ban-server/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" in another shell session and observe if additional informative error messages appear in the terminals.2023-02-08 19:38:24,663 fail2ban.actions [49680]: ERROR Failed to execute ban jail 'sshd' action 'iptables-multiport' info 'ActionInfo({'ip': '183.99.143.30', 'family': 'inet4', 'fid': at 0x7f1151a88790>, 'raw-ticket': at 0x7f1151a88e50>})': Error starting action Jail('sshd')/iptables-multiport: 'Script error'