Skip to content

traefik: point to plugin v1.8.1 (1.8.x line), add Docker Compose and bot detection - #1198

Open
mathieuHa wants to merge 3 commits into
crowdsecurity:mainfrom
mathieuHa:traefik-plugin-1.8
Open

mathieuHa wants to merge 3 commits into
crowdsecurity:mainfrom
mathieuHa:traefik-plugin-1.8

Conversation

@mathieuHa

@mathieuHa mathieuHa commented Oct 17, 2026 •

Copy link
Copy Markdown

Follow-up to maxlerebourg/crowdsec-bouncer-traefik-plugin#188, where we agreed to help keep the Traefik plugin documentation up to date here.

The Traefik pages now cover the plugin's 1.8.x line, the first stable releases with bot detection, and say so. The examples pin v1.8.1. v1.8.1 only fixes the version the plugin reports to the LAPI: v1.8.0 shows up as v1.7.1 in cscli bouncers list.

Changes

unversioned/bouncers/traefik.mdx

  • A note at the top: the page applies to every 1.8.x release, and the examples pin v1.8.1.
  • Plugin version v1.4.5 → v1.8.1, in the new Docker Compose example and the three Helm values. botdetection is back in the features, which matches the bot detection intro listing Traefik as compatible.
  • New Traefik with Docker Compose section, covering remediation and AppSec. Until now the page only covered Kubernetes.
  • New Bot detection section, in the same shape as the HAProxy SPOA one: collections, acquisition, and the three settings that break the challenge with no error in the logs:
    • the router must also match /crowdsec-internal;
    • the CSP headers middleware must be listed after the plugin;
    • crowdsecAppsecBodyLimit must stay above 0 and be large enough for the proof.

appsec/quickstart/traefik.mdx (docs/ and version-v1.8)

  • Plugin version bump to v1.8.1, and a sentence that the guide applies to every 1.8.x release.
  • crowdsecAppsecFailureBlock: a 401 or any other unexpected status always blocks. crowdsecAppsecUnreachableBlock: 502, 503 and 504 count as unreachable.
  • New crowdsecAppsecBodyLimit entry. A body the client aborted is answered 499 (client gone) or 400, and is neither banned nor counted as blocked (plugin Add Misp Feed Generator Docs #401).
  • A note that an AppSec captcha action uses captchaProvider, and is banned without one.

These all match the plugin's README for the 1.8.x line. Nothing changed in behaviour between v1.8.0 and v1.8.1.

Tested

The Docker Compose example was copied from the page as written and run with CrowdSec v1.8.1, Traefik v3.7, and plugin v1.8.1 downloaded from the catalog:

  • GET / returns 200, and GET /.env returns 403 (AppSec). No errors in the Traefik logs.
  • cscli bouncers list shows the bouncer as v1.8.1. With v1.8.0 it shows v1.7.1.
  • A decision for the IP read from the access log returns 403 within 60 s (45 s here).
  • With the bot detection section applied, curl gets <title>CrowdSec Challenge</title>, and /crowdsec-internal/challenge/fpscanner.js is served through the plugin.

The same run passed on v1.8.0 earlier today. The Amplify preview build passes; I did not run the Docusaurus build locally.

🤖 Generated with Claude Code

…ection

- Bump the plugin version from v1.4.5 to v1.8.0-alpha, the first release
  with bot detection, and restore the bot detection badge.
- Add a Docker Compose quickstart (remediation and AppSec), so the page
  is no longer Kubernetes only.
- Add a bot detection section: the acquisition, and the three settings
  that break the challenge without any error (router coverage of
  /crowdsec-internal, CSP middleware order, crowdsecAppsecBodyLimit).
- AppSec quickstart: a 401 or any other unexpected status always blocks,
  and 502, 503 and 504 count as unreachable.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@aws-amplify-eu-west-1

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1198.d1to60jd2gb6y6.amplifyapp.com

- Pin the plugin to v1.8.0 instead of v1.8.0-alpha, in the Docker
  Compose example, the three Helm values and both AppSec quickstarts.
- AppSec quickstart: document crowdsecAppsecBodyLimit, and that a body
  the client aborted is answered 499 or 400 without a ban. Note that an
  AppSec captcha action needs captchaProvider, and is banned without it.
- Bot detection: the body limit must also be large enough for the proof,
  or the proof is cut short.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mathieuHa mathieuHa changed the title traefik: point to plugin v1.8.0-alpha, add Docker Compose and bot detection traefik: point to plugin v1.8.0, add Docker Compose and bot detection Oct 18, 2026
- Pin the plugin to v1.8.1 in the Docker Compose example, the three
  Helm values and both AppSec quickstarts. v1.8.1 only fixes the version
  the plugin reports to the LAPI: v1.8.0 reported itself as v1.7.1.
- State that the bouncer page and the AppSec quickstart apply to every
  1.8.x release of the plugin.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mathieuHa mathieuHa changed the title traefik: point to plugin v1.8.0, add Docker Compose and bot detection traefik: point to plugin v1.8.1 (1.8.x line), add Docker Compose and bot detection Oct 18, 2026
@mathieuHa
mathieuHa marked this pull request as ready for review October 18, 2026 12:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant