-
Hey all, my f2b has been working great for awhile. It's running in Docker (Portainer) protecting a self hosted Bitwarden server. Just upgraded to f2b 1.1.0 and now I get the following error when I test a ban:
Any help is appreciated, regards. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi all, Same history in Version: 7.2.1-69057 Update 5 on my Synology ( f2b dockerised ) iptables v1.8.10 |
Beta Was this translation helpful? Give feedback.
-
Related to this https://askubuntu.com/a/1428222 - No idea what is wrong with iptables here, but neither it is fail2ban issue, nor newer version of fail2ban changed something by iptables-actions. And because it looks anyway like a fail2ban/config/paths-debian.conf Lines 12 to 13 in c04e12d So either remove your own |
Beta Was this translation helpful? Give feedback.
Related to this https://askubuntu.com/a/1428222 -
iptables-legacy
could fix that, however I don't think it is good idea.No idea what is wrong with iptables here, but neither it is fail2ban issue, nor newer version of fail2ban changed something by iptables-actions.
And because it looks anyway like a
iptables-nft
layer (allowing iptables syntax with the nf_tables kernel subsystem), better would be to switch to nftables native actions instead, like fail2ban does it now by default for debians now...fail2ban/config/paths-debian.conf
Lines 12 to 13 in c04e12d
So either remove your own
banaction
oraction
…