Hi
When in the portal going to "Settings" and then "Logs" the following is diplayed
"Could not read file fail2ban.log!"
Restarting fail2ban with systemctl restart fail2ban.service cures it until next time.
From what I have read it is the log rotation that leaves fail2ban looking for the pre rolled log files.
Where would be the best place to cause a reload of fail2ban? It the end of the log rotate script or a cron job nightly to reload?
A reload will cause it to drop existing listed IP addresses.
I don't think it matters much which you use. I would probably choose cron just because it's easier.