You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
I'm running mssql and fail2ban on same docker-compose file. Fail2ban does not automatically ban the ip address of failed login (after max3). But when you restart the fail2ban container, it reads the log file and performs the ban. then after startup, it just sits there.
Expected behaviour
Fail2ban should ban the Ip Address after [maxretry] failed attempt without restarting the container.
Actual behaviour
After [maxretry] failed attempt, fail2ban does NOT ban the ip address.
You have to restart the fail2ban container for fail2ba to ban the ip address.
Steps to reproduce
Run the docker compose up
Try to login with invalid credential to mssql, 4 times.
Nothing happen. It does not ban the IP. Check the fail2ban docker log,, endless loop of this log
2024-07-02 06:28:40,866 fail2ban.actions [1]: HEAVY Actions: wait for pending tickets 2 (default 2)
2024-07-02 06:28:42,866 fail2ban.actions [1]: HEAVY Actions: check-unban 20, bancnt 0, max: 20
2024-07-02 06:28:42,866 fail2ban.actions [1]: HEAVY Actions: wait for pending tickets 2 (default 2)
2024-07-02 06:28:43,366 fail2ban.transmitter [1]: HEAVY Command: ['ping']
But Restart the fail2ban container, it reads the log file and bans the Ip correctly.
then container is still running but same problem again.
Support guidelines
I've found a bug and checked that ...
Description
I'm running mssql and fail2ban on same docker-compose file. Fail2ban does not automatically ban the ip address of failed login (after max3). But when you restart the fail2ban container, it reads the log file and performs the ban. then after startup, it just sits there.
Expected behaviour
Fail2ban should ban the Ip Address after [maxretry] failed attempt without restarting the container.
Actual behaviour
After [maxretry] failed attempt, fail2ban does NOT ban the ip address.
You have to restart the fail2ban container for fail2ba to ban the ip address.
Steps to reproduce
Docker info
Docker Compose config
Logs
Additional info
Environment:
jail.d/jail.local
I've tried it in windows docker desktop and ubuntu docker both produce same results
The text was updated successfully, but these errors were encountered: