This is due to YunoHost 3 migration that implies the deletion of fail2ban configuration files. See this forum post for a workaround/explanation
1 Like
This is due to YunoHost 3 migration that implies the deletion of fail2ban configuration files. See this forum post for a workaround/explanation