Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

By default only do captcha in cf bouncer #488

Closed
wants to merge 2 commits into from
Closed

By default only do captcha in cf bouncer #488

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
acffb38
by default only do captcha in cf bouncer
sbs2001 Nov 2, 2023
b472ee0
fix reveiw
sbs2001 Nov 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions crowdsec-docs/docs/bouncers/cloudflare-workers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,16 @@ You can run `sudo crowdsec-cloudflare-worker-bouncer -g <CLOUDFLARE_TOKEN1>,<CLO

:::

:::note
By default the generated config only sets up challenge remediation for all the zones.
You can change this by editing `cloudflare_config.accounts[*].zones[*].actions` and `cloudflare_config.accounts[*].zones[*].default_action` in the config to support ban action. Or make ban action the default.

To support ban and captcha remediations simultaneously, you can set `cloudflare_config.accounts[*].zones[*].actions` to `["captcha", "ban"]`
IP's originating from decisions with `captcha` action would be handled by captcha remediation and decisions with `ban` action would be handled by ban remediation.

Decisions with other actions would be applied remedications specified by `cloudflare_config.accounts[*].zones[*].default_action` value.
:::

### Manual Installation

#### Assisted
Expand Down