{% extends "dashboard.html" %} {% block head %} {% endblock %} {% block content %}

CrowdSec operator

Inspect each configured CrowdSec engine and investigate an IP across current and captured evidence.

CrowdSec connection

The selected connection applies to decisions, allowlists and IP investigation below.

Investigate an IP

Current CrowdSec decisions are checked alongside local bans and captured reports.

Active decisions

This is current state read directly from the selected CrowdSec engine.

Target Type Origin Scenario Duration Actions
Current state

Current state may change after this observation.

This covers the selected CrowdSec connection and BunkerWeb's own bans. Other protections are not checked here, and evidence that could not be read is no proof that this IP is permitted.

Current CrowdSec decisions
Current local BunkerWeb bans
Available CrowdSec alert evidence
Recent BunkerWeb reports

Captured report data describes what was observed at request time; it does not prove the current decision state.

CrowdSec allowlists

Trusted IPs and networks for the selected engine. These exceptions apply across its connected services and bouncers.

You can browse allowlists and check IPs here. To add or remove entries, use cscli on the CrowdSec engine.

How to manage trusted IPs and networks

Requires CrowdSec 1.7 or later. Run these commands on the host or inside the container running the selected engine's Local API (LAPI), with access to its CrowdSec configuration and database. Replace the example list name, IP and network with your own.

  1. Create a list once, or use an existing locally managed list.

    cscli allowlists create bunkerweb-trusted --description "Trusted IPs"

  2. Add trusted IPs or CIDR networks.

    cscli allowlists add bunkerweb-trusted 203.0.113.42 203.0.113.128/25 --expiration 24h --comment "Temporary access"

    This example expires after 24 hours. Omit --expiration for an entry that does not expire. IPv4 and IPv6 are supported.

  3. Inspect the list and its expiry dates.

    cscli allowlists inspect bunkerweb-trusted

  4. Remove an exception when it is no longer needed.

    cscli allowlists remove bunkerweb-trusted 203.0.113.42 203.0.113.128/25

After a change, refresh allowlists and investigate the IP again. Removing an exception permits future CrowdSec decisions; it does not create a ban. Local BunkerWeb bans and other protections remain separate.

Edit Console-managed lists in the CrowdSec Console.

CrowdSec allowlist documentation
{% endblock %} {% block scripts %} {% endblock %}