-
-
Notifications
You must be signed in to change notification settings - Fork 2k
fail2ban not working #2327
Copy link
Copy link
Closed
Labels
meta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/help wantedThe OP requests help from others - chime in! :DThe OP requests help from others - chime in! :Dmeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/lowservice/security/fail2ban
Metadata
Metadata
Assignees
Labels
meta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/help wantedThe OP requests help from others - chime in! :DThe OP requests help from others - chime in! :Dmeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/lowservice/security/fail2ban
Subject
Other - fail2ban
Description
I've just deployed docker-mailserver - Super nice!
I see that fail2ban is not working. I currently have set in
docker-compose.ymlhowever when I run
docker exec mailserver iptables -LI getI saw on #2169 that many are running fail2ban on their host instead. Are there any instructions for that?