canasta crowdsec reload

Restart the CrowdSec engine to apply changes

Synopsis

Restart the CrowdSec engine to apply pending changes without restarting the whole instance. Use it after accepting a console enrollment or after editing config/crowdsec/whitelists.yaml. On Compose only the engine container bounces, so the Caddy bouncer keeps enforcing its cached decisions throughout; on Kubernetes the engine is a sidecar in the Caddy pod, so the pod rolls and Caddy blips briefly. Note that community and console blocklists arrive on CrowdSec's own pull cycle (about every 2 hours), which a restart does not force.

After you unsubscribe a list — or delete the engine — in the Console, the engine keeps enforcing the IPs it already pulled from that list: they stay in its local decision DB and the Caddy bouncer keeps blocking them. It just stops receiving updates (a free-tier engine gets no reconcile, since that is a paid PAPI order). That frozen snapshot is usually fine to leave in place. Purge it only when you actually want to STOP blocking those IPs: add --purge-blocklist <name> (one list, by the name shown under "Console blocklists in effect" in canasta crowdsec status) or --purge-blocklists (all). Lists you are still subscribed to refill on the next pull cycle.

canasta crowdsec reload [flags]

Examples

canasta crowdsec reload
canasta crowdsec reload -i mysite
canasta crowdsec reload --purge-blocklist firehol_cruzit_web_attacks
canasta crowdsec reload --purge-blocklists

Flags

Flag	Shorthand	Description	Default	Orchestrator
`--id`	`-i`	Canasta instance ID	*	Both
`--purge-blocklist`		Stop blocking one console blocklist's cached IPs, by the name shown in status		Both
`--purge-blocklists`		Stop blocking all cached console-blocklist IPs		Both

* Defaults to the Canasta instance matching the current directory, if any.

Global flags

Flag	Shorthand	Description	Default	Required	Orchestrator
`--help`	`-h`	Show help message and exit			Both
`--verbose`	`-v`	Enable verbose output			Both