-
-
Notifications
You must be signed in to change notification settings - Fork 7
[BUG] fail2ban stopped working a while ago without me knowing #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
in the console of fail2ban docker i can see these rules: not of this is however visible on the host (also no chain) |
+1 |
I suspect that the rebase to Alpine 3.19 a couple of months ago may have caused this. According to https://www.alpinelinux.org/posts/Alpine-3.19.0-released.html
Whereas unraid uses As a test, I tried installing
then changed the
and now things are working again. Of course this is not a permanent solution (since an update to the docker image would again remove |
Facing the same issue in Unraid 6.12.4, so I have rolled back to the 1.0.2-r2-ls60 release before the rebase to Alpine 3.19 and this seems to have fixed it. To do this set the repository to Hopefully it can be addressed in a future release. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I seem to still be having this same issue in Snippet of error from
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue should probably stay open... |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is still not resolved, this bot is unhelpful. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
This issue is still a problem. The workaround from @danielaranki works for me, but it took me quite some time to get here.. Please fix or at least add something in the Documentation/Faq so that future users can find the workaround quicker :) |
Is there an existing issue for this?
Current Behavior
fail2ban has worked for me for quite a long time, so long that i stopped checking the logs for a while.
Now i can see in the logging that IP's are being banned as fail2ban logs says so, but it does not ban the ip really from the host side. I can just keep connecting even though i should be banned.
i can also no longer see the iptables on the unraid host. (expected a chain, but its not there)
Expected Behavior
No response
Steps To Reproduce
jail:
[authelia-auth]
enabled = true
#port = http,80,https,443,9091
#protocol = tcp
logpath = %(remote_logs_path)s/authelia/authelia.log
chain = DOCKER-USER
action = iptables-multiport[name=HTTP, port="http,https,9091,4443,18443,8181,7818,8080,1880", protocol=tcp]
#action = %(known/action)s
ignoreip = 127.0.0.1/8 ::1
172.18.0.0/16
192.168.0.0/24
bantime = -1
findtime = 24h
maxretry = 1
[nginx-bad-request]
enabled = true
#port = http,80,https,443,18443,1880,7818
logpath = %(nginx_access_log)s
chain = DOCKER-USER
action = iptables-multiport[name=HTTP, port="http,https,9091,4443,18443,8181,7818,8080,1880", protocol=tcp]
#action = %(known/action)s
ignoreip = 127.0.0.1/8 ::1
172.18.0.0/16
192.168.0.0/24
bantime = -1
findtime = 24h
maxretry = 1
error from logs:
2024-04-05 08:42:11,949 150AA2544B38 ERROR 150aa31018a0 -- exec: for proto in $(echo 'tcp' | sed 's/,/ /g'); do
iptables -w -D INPUT -p $proto -m multiport --dports http,https,9091,4443,18443,8181,7818,8080,1880 -j f2b-HTTP
done
iptables -w -F f2b-HTTP
iptables -w -X f2b-HTTP
2024-04-05 08:42:11,949 150AA2544B38 ERROR 150aa31018a0 -- stderr: "iptables v1.8.10 (nf_tables): Chain 'f2b-HTTP' does not exist"
2024-04-05 08:42:11,949 150AA2544B38 ERROR 150aa31018a0 -- stderr: "Try `iptables -h' or 'iptables --help' for more information."
2024-04-05 08:42:11,950 150AA2544B38 ERROR 150aa31018a0 -- stderr: 'iptables: No chain/target/match by that name.'
2024-04-05 08:42:11,950 150AA2544B38 ERROR 150aa31018a0 -- stderr: 'iptables: No chain/target/match by that name.'
2024-04-05 08:42:11,950 150AA2544B38 ERROR 150aa31018a0 -- returned 1
2024-04-05 08:42:11,950 150AA2544B38 ERROR Failed to stop jail 'nginx-bad-request' action 'iptables-multiport-f2b-HTTP': Error stopping action Jail('nginx-bad-request')/iptables-multiport-f2b-HTTP: 'Script error'
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: