sftp-fail2ban

SFTP Fail2ban is a Debian-based SFTP server container that runs OpenSSH with Fail2ban to harden secure file transfer against brute-force attacks for homelab…

  • Network Services
  • Security
  • Tools & Utilities
SFTP Fail2ban is a Debian-based SFTP server container that runs OpenSSH with Fail2ban to harden secure file transfer against brute-force attacks for homelab users.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

45/100 Fair

Maintained
72last commit 21 days ago
Popular
102 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 29 days ago

GitHub stars
2
Open issues
0
Last commit
2026-10-30
License
MIT
Activity
rising

Checked 17 days ago - source: GitHub (bmartino1/sftp2)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the SFTP login details first Before starting, provide the SFTP server address, port (the number that tells your computer where to send the SFTP traffic, often 22), username, and password. If any of these are missing or wrong, the app can't sign in and will fail to do its work. source
  • Match the SFTP port exactly Most SFTP servers use port 22, but if yours uses a different port, put that number in the port setting or SFTP_PORT. Using the wrong port means the app can't reach the server, even if the other details are correct. source
  • Keep credentials out of code files The examples load settings from a .env file, a small text file, which keeps the host, username, password, and port outside the main program. That is safer than leaving passwords in code, where they are easier to copy or share by accident. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does Fail2ban protect an SSH/SFTP endpoint from brute-force attempts?

Fail2ban scans log files such as auth.log and bans IP addresses that cause too many failed login attempts. It updates firewall rules to reject new connections from those IPs for a configurable period.

Which port do SFTP clients normally need to use?

Most SFTP servers use port 22. If the server is configured for a different port, clients must use that exact port.

Where should SFTP connection details be stored?

Store the host, username, password, and port in a .env file or environment rather than in code. This keeps credentials outside the main program and reduces accidental sharing.

What security issue is linked to the SFTP project discontinuation in the support page?

The Unraid support page notes the SFTP project was discontinued due to an OpenSSH CVE.

Answers sourced from forums.unraid.net, github.com, www.npmjs.com

Community

Collected 48 days ago - public community threads