CrowdSec Traefik Bouncer

CrowdSec Traefik Bouncer is a self-hosted CrowdSec bouncer for Traefik that protects services by blocking malicious client IPs.

  • Security
CrowdSec Traefik Bouncer is a self-hosted CrowdSec bouncer for Traefik that protects services by blocking malicious client IPs. It uses Traefik's ForwardAuth middleware to query CrowdSec with each client IP, returning HTTP 403 for banned clients and allowing other requests to continue.

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.

19/100 Low

Maintained
0last commit 1504 days ago
Popular
50332 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
08 serious findings, 7 minor, CI, tests

Based on 4 of 5 factors.

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

GitHub stars
332
Open issues
21
Last commit
2022-10-09
License
MIT
Activity
stale

Checked 20 days ago - source: GitHub (fbonalair/traefik-crowdsec-bouncer)

Resources & Compatibility

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

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

First-install notes

  • Replace the placeholder tokens Run the bouncer command with -g <TOKEN1>,<TOKEN2> replaced by your real CrowdSec tokens, which are the secret keys it uses to talk to your CrowdSec account. If you leave the placeholders in, the bouncer cannot ask CrowdSec who to block, so your setup will not protect anything. source
  • Edit the generated config before starting The command writes a YAML config (a plain-text settings file), usually under /etc/crowdsec/bouncers/. Edit it to match your CrowdSec endpoint, tokens, and other settings before starting the service; if the file is wrong or incomplete, the bouncer may start but still fail to enforce bans. source
  • Use sudo and start the service Run the install and start steps with sudo, which asks for admin rights, because the bouncer writes to /etc and may use systemd (the Linux service manager). If you skip sudo or never start the service, installation can fail with permission errors or the bouncer will not keep running in the background. source
  • CrowdSec prerequisite Install CrowdSec before deploying the Traefik bouncer. source

Fetched 37 days ago - each note links to its source

Alternatives (5)

  • Cloudflare - Protects websites with front-end proxy, dynamic DNS, CDN, and firewall; blocks DDoS and targeted attacks, optimizes traffic, and analyzes t…
  • CrowdSec - CrowdSec is a free, open-source IDS/IPS and WAF that detects malicious behavior by analyzing server logs and HTTP requests, then blocks off…
  • Fail2ban - Fail2ban is a daemon that monitors log files and automatically bans hosts that cause multiple authentication failures, using firewall rules…
  • IPBanPro - IPBan is a FREE and open source application that allows auto banning ip addresses from failed login attempts.
  • defensia-agent

Checked 41 days ago - source: AlternativeTo

Common questions

What connectivity is required when hosting the fbonalair Traefik bouncer container?

The bouncer must be able to reach CrowdSec and must also be reachable by Traefik.

Do older guides that mention ForwardAuth or cloudFlareIPs still match current Traefik bouncer setup?

No, the source notes that ForwardAuth is gone and there are no more cloudFlareIPs entries in Traefik config files.

Should the bouncer use streaming mode for better performance?

Streaming mode is recommended for performance, with decisions updated every 60 seconds by default.

Should a CrowdSec bouncer be installed on every downstream web server instead of only Traefik?

It should usually run on the internet-facing main entrance, such as Traefik, rather than on every downstream web server. A router or firewall agent can be used if supported.

Answers sourced from discourse.crowdsec.net, github.com, www.reddit.com, www.reddit.com

Community

Collected 53 days ago - public community threads