I’m going to horn in on this thread because perhaps Brook will run into the same problems I have and will then have the same questions I do.
As mentioned in a previous thread I’m evaluating the GPL version before going Pro. With AskewDread’s help I solved my other issue (thank-you again), but I’m having difficulty with fail2ban, also on a CentOS 7 system.
I first attempted to install fail2ban via Webmin, but that failed because I hadn’t installed EPEL per the instructions at https://www.virtualmin.com/documentation/security/fail2ban . So I did that and then Webmin was able to install fail2ban, along with a bunch of dependencies. So far, so good.
Then the problems started.
I clicked through to the now active fail2ban module and started fail2ban. According to “ps” this appears to have been successful. Then I attempted to configure it to start at boot. Each time the page refreshed, “No” was still selected. So I moved on.
Contrary to the documentation linked to above, the SSH monitoring shows as disabled under “Filter Action Jails”. When I tried to enable it I got the following error:
Failed to save jail : All log files must be absolute paths or patterns
All I did was click “Yes” next to “Currently enabled?” and then the “Save” button, leaving all of the default settings in place. Am I supposed to change the default settings? Which ones?
I tried activating a couple of other jails in the same way and received exactly the same error each time. Something is not working.
Back at the full list of jails, while one can select multiple jails, there doesn’t seem to be a way to activate them at the same time. Do I really have to activate them one at a time?! Regardless, I’m getting the above error when I try anyway.
Simply put, fail2ban doesn’t seem to be working on my server. I can’t configure it (through Webmin anyway) to start on boot, and I cannot activate any of the filter actions.
Anyone have any ideas? Thanks.