[Fail2ban-users] No one banned, ports block

[Tom M. <tm...@sp...>]

Hi

I am trying to set up fail2ban on Awslinux 2023 (which is a fedora spin) on EC2.  To start with, the service that I am trying to protect is running and I can connect to it from the outside world on a port in the 7000 range.  I then install fail2ban and start it out of the box with no local changes.  At this point, freshly installed, I can still reach the port from the outside world.

If I reboot the instance, my port is now unreachable from the outside.  Note that I did not enable fail2ban as a service, so it is not even running in the rebooted instance.  If I start or stop fail2ban nothing changes, at this point the port seems blocked.

If I uninstall fail2ban (dnf remove fail2ban) then the port is accessible again.

Note that this is with no changes to the config files, just plain out of the box.

Does anyone have an idea of what is going wrong here?  If seems to work ok initially, but after the first reboot the port is blocked.  Ssh still works, so it is not like all ports are blocked.  I do notice that some of the aws ec2 monitoring is not reporting, so perhaps other ports are blocked as well.

Thanks,
Tom