Missing key 'banaction' in configuration

[Funk66]

The commenting out of the 'banaction' variable in commit 0a1f92c breaks at least some jails with default settings, like sshd. The line action_ = %(banaction)s... in jail.conf requires that variable:

ERROR   Failed during configuration: Bad value substitution: option 'action' in section 'sshd' contains an interpolation key 'banaction' which is not a valid option name. Raw value: '%(action_)s'

[ABEIDO]

My logs is getting crazy spam with this. I went back to the container lscr.io/linuxserver/fail2ban:1.1.0-r2-ls19 and that worked as a temporary fix.

[Funk66]

@ABEIDO, you can also add the missing declaration to your config. Something like this:

banaction          = nftables
banaction_allports = nftables[type=allports]

[ABEIDO]

@Funk66

Thanks for the tip.

I edited the jail.local from
banaction = %(banaction_allports)s

to
#banaction = %(banaction_allports)s
banaction = nftables
banaction_allports = nftables[type=allports]

It seems to wok, but is there any diffrence in function?

[Funk66]

There should be no difference in functionality - nftables can work as a drop-in replacement for iptables, and will be the new default banaction in fail2ban v1.1.1. That said, I haven't looked into how this all is implemented internally.

[HawaiianPizza]

EDIT: Ok, I didn't realize [Default] had to be in ALL-CAPS. Changing it to [DEFAULT] fixed it.

Has this been fixed yet? I tried adding @Funk66's suggestion into my jail.local file and it didn't fix anything.

My jail.local, which is located in the same directory as the jail.conf file, looks like this:

[Default]
banaction = nftables
banaction_allports = nftables[type=allports]

[mpkossen]

The absence of banaction configuration in some cases result in a non-functional/restarting container. This could be confusing to new users. Perhaps we can include a note about this in the README in case the banactions are left out of the default config?

[StarWing01]

Totally agree =) I'm new to fail2ban in docker, and I want to build a test jail for my Emby-docker, but fails completely with error above when "docker compose up".