Fail2Ban is a daemon which runs in the backend and analyzes log files. This can be ssh logs for bruteforce attacks, but in fact useless when using keys. Also it can interact with logs of apache, nginx and stuff.
In fact Fail2Ban interacts with iptables and blocks IPs if for example someone tried to bruteforce your login on application xyz.
I dont know if I understand it correctly or misunderstood the whole concept.
But as i understand it is it a background service there keeping an eye on failed login attempts on my HA and blocks login attempts from the IP address for some time.
If that is the case i have a few things i wish it to keep an eye on.
can you be a little more precise what you did so far? Have you enabled fail2ban? You have to mv or cp the .conf to .local in /etc/fail2ban
Have you created the jail for hass? What do the logs of fail2ban say?
etc…
I’m on the HASSOS on a raspberry pi 3B+
As i understand it from the official guide should fail2ban be integrated to the system (may be that I’m wrong) so as i stater i created the fail2ban.log and pointed to it (the file is empty)
I then created the code above in my configuration file.
I later tried to put the following code in do to i read in another official guide that i needed to implement some http binding i will call it.
When you are already root you dont need to use the “sudo”.
But in fact I have no idea how hassOS is build. I use a normal linux system for my setup, as I have more control over everything. But this is not recommended for beginners I would say.
Even not sure if hassOS is using docker images for HA and so on. Because this would have even a different setup then on fail2ban. Maybe anyone else can tell you more.
I’m not sharp in Linux my self but I’m not new to it. I have made webservers in CentOS and used Ubuntu and mint to play around in on client machines.
But the reason for the pi in this setup is do to i had a few laying around that i did not use and stumbled over this fine software and then started to expand on my smart devices.
Back on topic.
When i look in the supervisor log then there’s som lines about ducker.
So maybe there’s a kind of docker implementation in the software.
But can be that the structure of the OS isolate parts for security.