I noticed that when a ran dietpi-services the fail2ban service was ‘inactive’.
It starts without issues.
today I took the time to see what could be the cause of the inactive fail2ban service and it turned out that when fail2ban service mode is set to be controlled by dietpi (recommended) and setting for Include = included fail2ban fails to start after a reboot.
So I needed to start it manually.
now when I set the mode to controlled by systemd (and included = included), the fail2ban startup okay after a reboot.
Not sure if that is a bug or a combination of other services I have that conflict on startup (e.g. I use UFW as firewall).
So just posting here as i have fixed this with the settings above and maybe somebody else runs into this
And I think that fail2ban cannot be controleld by dietpi-services as it is listed in an array with the following comment (in /boot/dietpi/dietpi-services)
# Non-controlled services: Only show in menu and/or status mode!
so although you can set it as dietpi controlled, that setting has no effect. It should be systemd controlled (So maybe that is the default setting when installing, no idea: have been playing with these settings to much I think :))