I'm currently trying to get Fail2ban to work with my Xibo container, but even though I'm listed as banned, I can still attempt to log in.
debian@vps-ec7a07fd:~/xibo$ sudo fail2ban-client status xibo
Status for the jail: xibo
|- Filter
| |- Currently failed: 1
| |- Total failed: 7
| `- File list: /var/log/xilog/container.log
`- Actions
|- Currently banned: 1
|- Total banned: 1
`- Banned IP list: 172.18.0.1
I went to check the IPtables, but I don't see anything unusual.
pkts bytes target prot opt in out source destination
32 6227 f2b-xibo 6 -- * * 0.0.0.0/0 0.0.0.0/0
multiport dports 80,443
And finally, I don't see any errors in the fail2ban.log.
2025-02-21 12:35:55,883 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:35:55
2025-02-21 12:35:57,813 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:35:57
2025-02-21 12:36:00,516 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:35:59
2025-02-21 12:36:00,674 fail2ban.actions : NOTICE [xibo] Ban 172.18.0.1
2025-02-21 12:36:02,119 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:36:01
2025-02-21 12:36:03,743 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:36:03
2025-02-21 12:36:05,501 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:36:05
2025-02-21 12:36:05,904 fail2ban.actions : NOTICE [xibo] 172.18.0.1 a
lready banned
2025-02-21 12:36:07,244 fail2ban.filter : INFO [xibo] Found
172.18.0.1 - 2025-02-21 12:36:07
2025-02-21 12:39:05,184 fail2ban.actions : NOTICE [xibo] Unban
172.18.0.1
If you have any idea where the issue might come from, I'm open to any suggestions.
Asked by Jean
(21 rep)
Feb 21, 2025, 01:04 PM
Last activity: Feb 21, 2025, 03:46 PM
Last activity: Feb 21, 2025, 03:46 PM