Fail2ban
Container
Fail2ban is a daemon to ban hosts that cause multiple authentication errors.
Image details
Configuration
TypeContainerlinuxlinuxserver/fail2ban:latest80:80/tcp/config : /srv/lsio/fail2ban/config/var/log:ro : /srv/lsio/fail2ban/var/log:ro/remotelogs/airsonic:ro : /srv/lsio/fail2ban/remotelogs/airsonic:ro/remotelogs/apache2:ro : /srv/lsio/fail2ban/remotelogs/apache2:ro/remotelogs/authelia:ro : /srv/lsio/fail2ban/remotelogs/authelia:ro/remotelogs/emby:ro : /srv/lsio/fail2ban/remotelogs/emby:ro/remotelogs/filebrowser:ro : /srv/lsio/fail2ban/remotelogs/filebrowser:ro/remotelogs/homeassistant:ro : /srv/lsio/fail2ban/remotelogs/homeassistant:ro/remotelogs/lighttpd:ro : /srv/lsio/fail2ban/remotelogs/lighttpd:ro/remotelogs/nextcloud:ro : /srv/lsio/fail2ban/remotelogs/nextcloud:ro/remotelogs/nginx:ro : /srv/lsio/fail2ban/remotelogs/nginx:ro/remotelogs/nzbget:ro : /srv/lsio/fail2ban/remotelogs/nzbget:ro/remotelogs/overseerr:ro : /srv/lsio/fail2ban/remotelogs/overseerr:ro/remotelogs/prowlarr:ro : /srv/lsio/fail2ban/remotelogs/prowlarr:ro/remotelogs/radarr:ro : /srv/lsio/fail2ban/remotelogs/radarr:ro/remotelogs/sabnzbd:ro : /srv/lsio/fail2ban/remotelogs/sabnzbd:ro/remotelogs/sonarr:ro : /srv/lsio/fail2ban/remotelogs/sonarr:ro/remotelogs/unificontroller:ro : /srv/lsio/fail2ban/remotelogs/unificontroller:ro/remotelogs/vaultwarden:ro : /srv/lsio/fail2ban/remotelogs/vaultwarden:roPUID=1000PGID=1000TZ=Etc/UTCVERBOSITY=-vvunless-stoppedTemplate by technorabilia
Notes
Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.
mkdir -p /srv/lsio/fail2ban/config
mkdir -p /srv/lsio/fail2ban/var/log:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/airsonic:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/apache2:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/authelia:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/emby:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/filebrowser:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/homeassistant:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/lighttpd:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/nextcloud:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/nginx:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/nzbget:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/overseerr:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/prowlarr:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/radarr:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/sabnzbd:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/sonarr:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/unificontroller:ro
mkdir -p /srv/lsio/fail2ban/remotelogs/vaultwarden:ro
Standalone Install
Select an install method, to see config/commands for deploying Fail2ban
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Fail2ban, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.

The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
linuxserver/fail2ban
Fail2ban is a daemon to ban hosts that cause multiple authentication errors.

Supported Architectures
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.Simply pulling
lscr.io/linuxserver/fail2ban:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-\ |
| arm64 | ✅ | arm64v8-\ |
Application Setup
This container is designed to allow fail2ban to function at the host level, as well as at the docker container level. If you are running applications on the host, you will need to set thechain to INPUT in the jail for that application.Configuration Files
On first run, the container will create a number of folders and files in/config. The default configurations for fail2ban are all disabled by default.Please refer to the Configuration README, which can be viewed in our repository, or in your config folder at
/config/fail2ban/README.md.Remote Logs
All jails require the ability to read the application log files. We recommend mounting each application's log folder as a volume to the container (illustrated by the optional volumes in our documentation). Mounting individual log files can cause issues and is not recommended.The
/remotelogs path is designed to act as a parent for all log files you would like fail2ban to be able to use.
Each log file should be mounted in a subfolder underneath /remotelogs, ex:/remotelogs/nginx/would mount a folder containing the nginx logs to the container
Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.
docker-compose (recommended, click here for more info)
---
services:
fail2ban:
image: lscr.io/linuxserver/fail2ban:latest
container_name: fail2ban
cap_add:
- NET_ADMIN
- NET_RAW
network_mode: host
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- VERBOSITY=-vv #optional
volumes:
- /path/to/fail2ban/config:/config
- /var/log:/var/log:ro
- /path/to/airsonic/log:/remotelogs/airsonic:ro #optional
- /path/to/apache2/log:/remotelogs/apache2:ro #optional
- /path/to/authelia/log:/remotelogs/authelia:ro #optional
- /path/to/emby/log:/remotelogs/emby:ro #optional
- /path/to/filebrowser/log:/remotelogs/filebrowser:ro #optional
- /path/to/homeassistant/log:/remotelogs/homeassistant:ro #optional
- /path/to/lighttpd/log:/remotelogs/lighttpd:ro #optional
- /path/to/nextcloud/log:/remotelogs/nextcloud:ro #optional
- /path/to/nginx/log:/remotelogs/nginx:ro #optional
- /path/to/nzbget/log:/remotelogs/nzbget:ro #optional
- /path/to/overseerr/log:/remotelogs/overseerr:ro #optional
- /path/to/prowlarr/log:/remotelogs/prowlarr:ro #optional
- /path/to/radarr/log:/remotelogs/radarr:ro #optional
- /path/to/sabnzbd/log:/remotelogs/sabnzbd:ro #optional
- /path/to/sonarr/log:/remotelogs/sonarr:ro #optional
- /path/to/unificontroller/log:/remotelogs/unificontroller:ro #optional
- /path/to/vaultwarden/log:/remotelogs/vaultwarden:ro #optional
restart: unless-stoppeddocker cli (click here for more info)
docker run -d \
--name=fail2ban \
--net=host \
--cap-add=NET_ADMIN \
--cap-add=NET_RAW \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e VERBOSITY=-vv `#optional` \
-v /path/to/fail2ban/config:/config \
-v /var/log:/var/log:ro \
-v /path/to/airsonic/log:/remotelogs/airsonic:ro `#optional` \
-v /path/to/apache2/log:/remotelogs/apache2:ro `#optional` \
-v /path/to/authelia/log:/remotelogs/authelia:ro `#optional` \
-v /path/to/emby/log:/remotelogs/emby:ro `#optional` \
-v /path/to/filebrowser/log:/remotelogs/filebrowser:ro `#optional` \
-v /path/to/homeassistant/log:/remotelogs/homeassistant:ro `#optional` \
-v /path/to/lighttpd/log:/remotelogs/lighttpd:ro `#optional` \
-v /path/to/nextcloud/log:/remotelogs/nextcloud:ro `#optional` \
-v /path/to/nginx/log:/remotelogs/nginx:ro `#optional` \
-v /path/to/nzbget/log:/remotelogs/nzbget:ro `#optional` \
-v /path/to/overseerr/log:/remotelogs/overseerr:ro `#optional` \
-v /path/to/prowlarr/log:/remotelogs/prowlarr:ro `#optional` \
-v /path/to/radarr/log:/remotelogs/radarr:ro `#optional` \
-v /path/to/sabnzbd/log:/remotelogs/sabnzbd:ro `#optional` \
-v /path/to/sonarr/log:/remotelogs/sonarr:ro `#optional` \
-v /path/to/unificontroller/log:/remotelogs/unificontroller:ro `#optional` \
-v /path/to/vaultwarden/log:/remotelogs/vaultwarden:ro `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/fail2ban:latestParameters
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.| Parameter | Function |
|---|---|
--net=host | Shares host networking with container. |
-e PUID=1000 | for UserID - see below for explanation |
-e PGID=1000 | for GroupID - see below for explanation |
-e TZ=Etc/UTC | specify a timezone to use, see this list. |
-e VERBOSITY=-vv | Set the container log verbosity. Valid options are -v, -vv, -vvv, -vvvv, or leaving the value blank or not setting the variable. |
-v /config | Persistent config files |
-v /var/log:ro | Host logs. Mounted as Read Only. |
-v /remotelogs/airsonic:ro | Optional path to airsonic log folder. Mounted as Read Only. |
-v /remotelogs/apache2:ro | Optional path to apache2 log folder. Mounted as Read Only. |
-v /remotelogs/authelia:ro | Optional path to authelia log folder. Mounted as Read Only. |
-v /remotelogs/emby:ro | Optional path to emby log folder. Mounted as Read Only. |
-v /remotelogs/filebrowser:ro | Optional path to filebrowser log folder. Mounted as Read Only. |
-v /remotelogs/homeassistant:ro | Optional path to homeassistant log folder. Mounted as Read Only. |
-v /remotelogs/lighttpd:ro | Optional path to lighttpd log folder. Mounted as Read Only. |
-v /remotelogs/nextcloud:ro | Optional path to nextcloud log folder. Mounted as Read Only. |
-v /remotelogs/nginx:ro | Optional path to nginx log folder. Mounted as Read Only. |
-v /remotelogs/nzbget:ro | Optional path to nzbget log folder. Mounted as Read Only. |
-v /remotelogs/overseerr:ro | Optional path to overseerr log folder. Mounted as Read Only. |
-v /remotelogs/prowlarr:ro | Optional path to prowlarr log folder. Mounted as Read Only. |
-v /remotelogs/radarr:ro | Optional path to radarr log folder. Mounted as Read Only. |
-v /remotelogs/sabnzbd:ro | Optional path to sabnzbd log folder. Mounted as Read Only. |
-v /remotelogs/sonarr:ro | Optional path to sonarr log folder. Mounted as Read Only. |
-v /remotelogs/unificontroller:ro | Optional path to unificontroller log folder. Mounted as Read Only. |
-v /remotelogs/vaultwarden:ro | Optional path to vaultwarden log folder. Mounted as Read Only. |
--cap-add=NETADMIN | Required for fail2ban to be able to modify iptables rules. |
--cap-add=NETRAW | Required for fail2ban to be able to bind to any interface & use RAW sockets. |
Portainer notice
This image utilisescap_add or sysctl to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prependFILE__.As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariableWill set the environment variable
MYVAR based on the contents of the /run/secrets/mysecretvariable file.Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional-e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.User / Group Identifiers
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance
PUID=1000 and PGID=1000, to find yours use id your_user as below:id your_userExample output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)Docker Mods
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info
- Shell access whilst the container is running:
```bash
docker exec -it fail2ban /bin/bash
```- To monitor the logs of the container in realtime:
```bash
docker logs -f fail2ban
```- Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' fail2ban
```- Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/fail2ban:latest
```Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.Below are the instructions for updating containers:
Via Docker Compose
- Update images:
* All images:
```bash
docker-compose pull
```
* Single image:
```bash
docker-compose pull fail2ban
```- Update containers:
* All containers:
```bash
docker-compose up -d
```
* Single container:
```bash
docker-compose up -d fail2ban
```- You can also remove the old dangling images:
```bash
docker image prune
```Via Docker Run
- Update the image:
```bash
docker pull lscr.io/linuxserver/fail2ban:latest
```- Stop the running container:
```bash
docker stop fail2ban
```- Delete the container:
```bash
docker rm fail2ban
```- Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
```bash
docker image prune
```Image Update Notifications - Diun (Docker Image Update Notifier)
>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:git clone https://github.com/linuxserver/docker-fail2ban.git
cd docker-fail2ban
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/fail2ban:latest .The ARM variants can be built on x8664 hardware and vice versa using
lscr.io/linuxserver/qemu-staticdocker run --rm --privileged lscr.io/linuxserver/qemu-static --resetOnce registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 11.02.25: - Rebase to Alpine 3.21.
- 12.10.24: - Rebase to Alpine 3.20.
- 05.03.24: - Rebase to Alpine 3.19.
- 01.06.23: - Add optional VERBOSITY environment variable, allowing users to set the container log verbosity.
- 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
- 15.12.22: - Replace unmaintained ssmtp with msmtp.
- 15.12.22: - Rebase to Alpine 3.17, Add ssmtp and whois packages. Symlink config to allow live reloading.
- 25.08.22: - Update README to clarify remote log information.
- 09.08.22: - Initial Release.
Serve Fail2ban on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying fail2ban.example.com to http://localhost:80
Add this to your Caddyfile
fail2ban.example.com {
reverse_proxy http://localhost:80
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs Fail2ban - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Runs on the host network
This container shares your server's network directly, so port mappings are ignored and every port the app opens binds straight to the host.
- If a port won't bind, find the clash with
sudo ss -tlnpand stop the other service, or change the port in Fail2ban's own settings.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:80. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, Fail2ban can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 80
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /srv/lsio/fail2ban/config(and the same for the other mapped folders) - Or set the
PUIDandPGIDvariables (defaults 1000:1000) to match your own user, found withid $USER
Image won't pull
Test the pull directly on the host: docker pull linuxserver/fail2ban:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect Fail2ban --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within Fail2ban's repo
- Template not working: Open an issue on technorabilia/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Fail2ban runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Fail2ban needs bundled into one download. This template pulls linuxserver/fail2ban:latest, which Docker fetches once (about 29 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Fail2ban's comes from Docker Hub, published by linuxserver.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.1.0. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 80:80 means it's reachable on port 80 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:80 in a browser. It opens:
80:80, likely the web interface
Volumes
A volume is where Fail2ban keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/configfrom/srv/lsio/fail2ban/configon the host/var/log:rofrom/srv/lsio/fail2ban/var/log:roon the host/remotelogs/airsonic:rofrom/srv/lsio/fail2ban/remotelogs/airsonic:roon the host/remotelogs/apache2:rofrom/srv/lsio/fail2ban/remotelogs/apache2:roon the host/remotelogs/authelia:rofrom/srv/lsio/fail2ban/remotelogs/authelia:roon the host/remotelogs/emby:rofrom/srv/lsio/fail2ban/remotelogs/emby:roon the host/remotelogs/filebrowser:rofrom/srv/lsio/fail2ban/remotelogs/filebrowser:roon the host/remotelogs/homeassistant:rofrom/srv/lsio/fail2ban/remotelogs/homeassistant:roon the host/remotelogs/lighttpd:rofrom/srv/lsio/fail2ban/remotelogs/lighttpd:roon the host/remotelogs/nextcloud:rofrom/srv/lsio/fail2ban/remotelogs/nextcloud:roon the host/remotelogs/nginx:rofrom/srv/lsio/fail2ban/remotelogs/nginx:roon the host/remotelogs/nzbget:rofrom/srv/lsio/fail2ban/remotelogs/nzbget:roon the host/remotelogs/overseerr:rofrom/srv/lsio/fail2ban/remotelogs/overseerr:roon the host/remotelogs/prowlarr:rofrom/srv/lsio/fail2ban/remotelogs/prowlarr:roon the host/remotelogs/radarr:rofrom/srv/lsio/fail2ban/remotelogs/radarr:roon the host/remotelogs/sabnzbd:rofrom/srv/lsio/fail2ban/remotelogs/sabnzbd:roon the host/remotelogs/sonarr:rofrom/srv/lsio/fail2ban/remotelogs/sonarr:roon the host/remotelogs/unificontroller:rofrom/srv/lsio/fail2ban/remotelogs/unificontroller:roon the host/remotelogs/vaultwarden:rofrom/srv/lsio/fail2ban/remotelogs/vaultwarden:roon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Fail2ban takes 4 of them, all with defaults you can leave alone or tweak:
PUID, defaults to1000. Run 'id [USER]' for the owner of the host volume directories to get the UID to use here.PGID, defaults to1000. Run 'id [USER]' for the owner of the host volume directories to get the GID to use here.TZ, defaults toEtc/UTC. Specify a timezone to use, see this list.VERBOSITY, defaults to-vv. Set the container log verbosity. Valid options are -v, -vv, -vvv, -vvvv, or leaving the value blank or not setting the variable. [OPTIONAL]
Restart policy
The restart policy here is unless-stopped, so Docker restarts Fail2ban after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Users and permissions
The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.
Networking
Fail2ban runs on the host network, so it shares your server's networking directly instead of getting a private one of its own. Its ports open straight on the server with no mapping in between.
Container name
Once it's deployed, Portainer names the container Fail2ban. That's what you'll spot in the containers list and use in commands like docker logs Fail2ban.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Fail2ban up. Add the template list to Portainer once, then deploying Fail2ban is a click rather than a wall of config.