"crowdsec init: while initializing LAPIClient: authenticate watcher (docker1old): API error: missing
How to prevent DDoS attacks
Mozilla/5.0 (X11; Linux x86_64; rv:1.9.7.20) Gecko/6496-09-22 17:26:38.382965 Firefox/3.6.7. I quickly created a scenario to block all old UAs; the scenario worked and there were alerts/decisions everywhere, it was impressive. But the problem is that I felt CrowdSe...duration_expr not working in profiles.yaml
duration_expr string but it causes crowdsec to fail to start with this error ...cscli decisions list -a and -i flag not working at the same time
--ip flag, we cannot use -a at the same time.
The IP search just gets ignored, and all decisions are listed.
Is this by design? Of course we can get around it using grep, but it'd much faster to filter in the cscli.
As far as I've tested, it works flawlessly with cscli alerts list though....log acquisition
probing or probbing ?

nginx lua bouncer crashes if it cannot reach out to LAPI even momentarily
question on issue reading logs from bunkerweb
image:
tag: "v1.6.11"...
Gotify shows me the ban, but crowdsec dashboard not

Get alerts linked to a fqdn
Crowdsec FW bouncer with nftables configured but I think Itβs not working
Newcomer's guide feedback

Use of nginx variables with AppSec
set $disable_appsec 1...Why is there no decision to this appsec alert
Appsec whitelist #2
Traefik, Bouncer plugin and firewall bouncer issues
Cant list allowlists?
How to allow bots access to some URLs but not others
Update chocolatey packages
Priority tag before syslog line...