r/CrowdSec • • Nov 17 '25

CrowdSec Block Friday is here 🎉

Post image
0 Upvotes

If you’ve been thinking about upgrading your security game… this is the moment 🎉

60% OFF CrowdSec Console Premium

Use code BLOCKFRIDAY25 at checkout and unlock:

• Stronger protection with premium blocklists to stop botnet & CVE attackers

• Real-time and custom blocklists

• Instant alerts of targeted attacks with the “Am I Under Attack?” feature

• API access + manual block/allow lists

https://app.crowdsec.net/

30% OFF the Blocklist Bundle

Great if you want earlier protection and way fewer alerts

• Block malicious IPs up to 60 days earlier

• Up to 80% less alert fatigue

• Daily rotation of 5% of malicious IPs

Just fill out the form and select Block Friday. https://www.crowdsec.net/contact-blocklists

We’d love to see our community take advantage of this. (until Deember 3rd)

Safer together! 💜


r/CrowdSec • • Jul 18 '26

general crowdsec.. just a simple task as whitelisting to difficult

Thumbnail
app.crowdsec.net
0 Upvotes

Currently several home servers are blocked in Crowdsec. Homeassistant, NAS, Docker all local IP's 10.10.x.x and 192.168.x.x

So i guessed there will be a simple methode to ad a whitelist in the application itself ( plugin in Opnsense)

But it seems i am to dumb to find the option. So i tried several commands from the prompt ( not secure at all!) to add those things.. to no avail it seems.

It should be a option in crowdsec to add a whitelist from the gui. Nothing difficult.

But maybe its worse and i am to dumb to find the option.. so any tip is welcome but better a simpeler GUI.


r/CrowdSec • • May 26 '24

Crowdsec blocked itself

0 Upvotes

Installed dovecot-spam and crowdsec blocked localhost 127.0.0.1! Unbelievable!

Cscli decisions delete I 127.0.0.1 doesn't work.


r/CrowdSec • • Sep 14 '24

Lifting my own Ban Costs money

0 Upvotes

i wanted to try my current cloudflare setup and started bruteforcing my own server.

Good news: it worked!

But now i am looked out, and lifting my own Ip as a ban costs 31$/month
or am I doing something wrong


r/CrowdSec • • May 13 '26

bug I think http probing scenario needs to go...

0 Upvotes

I'm just on a holiday and got banned again left and right (wifi, mobile, mobile + vpns) for using my services.

my internet is so slow right I'm struggling to find out why. I added my Ips to my allowlist and then it worked briefly. But I also ran into weird issues that made me reboot my VPS and ultimately led to a backup restore of my Pangolin setup. Briefly even my whitelisted home ip didn't work no idea why

I'm sorry I can't produce enough details as I had to fix my whole setup using an iphone and it was painful enough believe me...

What I realised is that the http-probing scenario - which I've disabled months prior- was reenabled. Probably through a CS upgrade I guess?

what's the point of this crap if it repeatedly blocks me and my other users from accessing simple services on m homelab?

is there no way to disable this thing for good??


r/CrowdSec • • Jun 15 '26

general Security Report "Attacks Prevented" rising exponentially

1 Upvotes

I'm getting concerned about the number of prevented attacks on my CrowdSec instance. It seems every time a report comes in, the number of attacks prevented is significantly higher than the previous period, with the highest vector being "unknown behavior".

December of last year, I was seeing ~220k attacks prevented per week on my VPS, and now I'm seeing ~750k. This seems like a RIDICULOUS number of attempts... Is this normal? Is this just due to a rise in automated bot/AI attacks? Is anyone else seeing this? Perhaps I'm being targeted specifically?

Curious what others' experiences are like.


r/CrowdSec • • Sep 04 '26

general Baned for no reason.

Post image
8 Upvotes

I don't know anything about this thing, but for some reason I can't Enter a specific page from my home network on my phone, (I haven't tested other devices). Could someone explain to me what is happening?

I'm using a pixel pro 6, android... 16 and this problem happens in All my cell phone browsers.

I have downloaded a lot of books, comics and manga but the page I can't enter is " biblioteca Cervantes", I don't know if this problem is because I didn't close the tab or what.


r/CrowdSec • • Sep 15 '25

general Can I set up Crowdsec on my NAS using Nginx and Cloudflare DDNS?

Thumbnail reddit.com
0 Upvotes

r/CrowdSec • • May 18 '24

How to integrate Crowdsec and caddy together

0 Upvotes

I have caddy installed using the linux installation script and also have Crowdsec installed using the script, I would like to allow Crowdsec to integrate with caddy so that caddy can be protected however I haven't seen any official documentation on how to get this running.

When searching the caddy hub I found a collection (https://app.crowdsec.net/hub/author/crowdsecurity/collections/caddy) and a bouncer (https://app.crowdsec.net/hub/author/hslatman/remediation-components/caddy-crowdsec-bouncer). I would like to know if I would need to install both of them to integrate caddy with Crowdsec or I only need to install one of them.

So far I have the collection installed and enabled however I don't know if it's actually protecting caddy and the lack of documentation is really leaving me confused on how to get this working so any help would be appreciated.


r/CrowdSec • • Oct 17 '25

general opnsense new install - install fails cant start services

0 Upvotes

Edit: solved by /u/guack-a-mole comment below. Thank you

i get this when i try to install
Updating crowdsec hub data Downloading /usr/local/etc/crowdsec/hub/.index.json Error: cscli hub update: failed to update hub: while writing to /usr/local/etc/crowdsec/hub/.index.json.1235591161.download: net/http: request canceled (Client.Timeout or context cancellation while reading body) Failed to update crowdsec hub data. You can run 'cscli hub update; cscli hub upgrade' to update manually, or let the cron job do it for you. Error: cscli hub list: invalid hub index: unable to read index file: open /usr/local/etc/crowdsec/hub/.index.json: no such file or directory. Run 'sudo cscli hub update' to download the index again Error: cscli parsers install: invalid hub index: unable to read index file: open /usr/local/etc/crowdsec/hub/.index.json: no such file or directory. Run 'sudo cscli hub update' to download the index again Error: cscli collections install: invalid hub index: unable to read index file: open /usr/local/etc/crowdsec/hub/.index.json: no such file or directory. Run 'sudo cscli hub update' to download the index again Starting crowdsec.


r/CrowdSec • • May 18 '26

bug Kaspersky blocks CrowdSec

Post image
2 Upvotes

I know, it's Kaspersky fault and not CrowdSecs, but it should be known that the Web Protection is blocking the Website


r/CrowdSec • • Jul 10 '26

general CrowdSec Troubleshooter — a Docker tool I built to actually diagnose why CrowdSec (+ Traefik) isn't blocking what you think it should

5 Upvotes

I've been running CrowdSec + Traefik for a while and got tired of the same debugging loop every time something didn't add up — is LAPI actually reachable, is the bouncer actually registered, is the decision actually in the ban list, is it actually reaching the bouncer, etc. So I built a small tool for it.

What is it?

CrowdSec Troubleshooter is a standalone, unprivileged Docker image that runs once (docker run --rm, no daemon, no docker.sock, no --privileged, no NET_ADMIN) and tells you exactly what's working and what isn't, tier by tier depending on what credentials you give it:

  • Tier 0 (nothing but the LAPI URL) — LAPI liveness, is it actually parsing logs, bouncer-type fingerprinting (legacy ForwardAuth bouncer vs the modern Traefik plugin), a heuristic on your LAPI URL itself, a cscli hub update/upgrade cron nag since nothing else keeps your scenarios current

  • Tier 1 (a read-only bouncer key) — look up a specific IP's ban status and why, plus an automatic ban-count summary broken down by scope/origin so you can actually see it's doing something

  • Tier 2 (a machine credential) — the real test: adds a real short-lived ban on itself, confirms the target actually returns 403, removes the ban, confirms access is restored. This is the one that actually proves blocking works end to end instead of just "looks configured"

  • Tier 3 (read-only host mounts) — DOCKER-USER iptables chain evidence (the #1 reported "ping blocked but HTTP gets through" issue), duplicate acquisition entries, compose-file hardening audit, syslog hinting

It also ships with a curated, offline knowledge base baked into the image — no internet needed to browse it — of ~30 real CrowdSec/Traefik gotchas pulled from a research pass across the top GitHub issues on the core crowdsec repo, the firewall bouncer, and the Traefik plugin repo, each with a link to the actual fix. docker run --rm modem7/crowdsec-troubleshooter issues to browse it.

There's also a wizard.sh if you don't want to hand-build docker run flags — it auto-detects your running CrowdSec container's compose file and pre-fills what it can.

Who it's for

Anyone self-hosting CrowdSec, especially fronted by Traefik. Works the same whether CrowdSec itself is Dockerized or a bare-metal/apt install — the troubleshooter is always a container, but it's just talking to LAPI over HTTP either way.

On the AI question

I used Claude for a chunk of the docs and some of the implementation, as well as code optimisation — not going to pretend otherwise. But it's not vibe-coded: everything went through shellcheck, a real bats test suite (100+ tests, mock LAPI servers, happy path + failure path for every check), and multiple bugs only got caught by actually running things against a real LAPI instance rather than trusting what looked right on paper (there's a whole section in the repo's DESIGN.md documenting where assumptions turned out wrong and how they were caught — including one where an endpoint I assumed existed turned out to not exist at all in the real API). I reviewed and tested every change before it shipped.

Links

Also on GHCR if you'd rather pull from there. Multi-arch (amd64/arm64). MIT licensed.

Feedback/issues/PRs welcome — it's still early days for some of the tiers (a couple of checks are flagged as unverified placeholders rather than pretending to work), but the core wellness check and live-block test are solid.


r/CrowdSec • • Oct 03 '26

bouncers CrowdSec not fit for purpose?

0 Upvotes

I've still been persevering with CrowdSec. I've determined the request patterns that can very accurately identify a large percentage of the unwanted traffic. I've created custom scenarios to filter for this and specified a range for both groupby and scope. The Range profile specifies 'ban'. I've installed the firewall bouncer on the host and specified the scenarios to use. After running it for a while, I find that the nftables aren't blocking ranges, they're blocking only a single IP. I then find these open issues on GitHub;

https://github.com/crowdsecurity/cs-firewall-bouncer/issues/412
https://github.com/crowdsecurity/crowdsec/issues/4517

This implies that the CrowdSec firewall bouncer is not and has never been capable of defending against a DDoS attack, or any other kind of malicious traffic that uses rotating IPs. Is that really the case?


r/CrowdSec • • Jan 01 '26

general Using CrowdSec on a very small VPS (Docker + Kamal proxy) — notes and questions

1 Upvotes

I’m running a very small VPS to host demos for my open source work.
Traffic is minimal (maybe 10–20 users), but after checking logs I saw constant SSH brute-force attempts and HTTP probing for .env, AWS credential paths, etc.

I ended up using CrowdSec to handle this.

A few notes from my setup:

  • SSH worked out of the box, no surprises there

  • HTTP was more work since logs come from a Kamal proxy inside Docker

  • I added a small custom parser to extract path, status, and source IP

  • Using the firewall bouncer with temporary bans (default behavior)

  • Notifications wired to Telegram so I can see when decisions happen

  • Everything automated so it’s repeatable on a fresh VPS

At first CrowdSec felt a bit heavy for such a small server, and not very obvious how to wire it with Kamal / container logs, but after some trial and error it worked well.

I wrote up what I learned here:
https://muthuishere.medium.com/securing-a-production-vps-in-practice-e3feaa9545af

Automation and config here (parsers + setup):
https://github.com/muthuishere/automated-crowdsec-kamal

Posting mainly to share the experience and to ask:

  • Is this a reasonable approach for small VPS setups?

  • Any improvements you’d suggest for Docker/Kamal-based logging?

  • Anything obvious I’m missing?

Happy to learn from others using CrowdSec in similar environments.


r/CrowdSec • • Jan 10 '25

general Simpliest way to install Crowdsec to protect my docker services

0 Upvotes

Hello Everyone,

I have a Debian VM running 2 docker containers :

- Caddy

- Nextcloud AIO

This VM is behind a pfSense CE firewall.

I would like to install Crowdsec but for the sake of simplicity I have 4 issues :

- I ideally dont want to install crowdsec directly on my OS, I prefer the docker way

- I ideally dont want to install crowdsec on pfsence (because Im not sure that package will be updated/maintained by crowdsec as much as the other plateforms)

- I ideally don't want to make a custom docker image to use the crowdsec module (just for the sake of keeping it simple) : so I guess I cannot use a bouncer for that service right ?

- Then, is it possible to install crowdsec just for the Nexcloud AIO container (which is behind caddy) ? Is there a bouncer for that service ?

Last question :

If installing crowdsec directly on the OS is a simpler setupfor me : will I be able to secure my main entry point which is Caddy reverse proxy's port ?

Thank for you help !

Here is my docker compose right now : 


r/CrowdSec • • Aug 03 '25

general Pangolin con crowdsec

Thumbnail reddit.com
0 Upvotes

r/CrowdSec • • Nov 13 '25

general Efficiently detect bot actions as per TLS JA4 Fingerprint

1 Upvotes

Hello !

I've deployed Crowdsec as a Daemonset on our GKE Clusters.
As we maintain an ecommerce website, we are prone to bot crawling or bruteforce.

That's why I'm having Crowdsec parse several logs from my website and APIs pods. These are JSON logs containing the remote User-agent, IP address, the GEOIP, the TLS JA3 fingerprint, the TLS JA4 fingerprint and other information.

Currently, my custom parsers and scenarios are deployed. These scenarios filters logs on IP address, TLS JA3 fingerprint or TLS JA4 fingerprint.

When a scenario threshold (capacity) is reached in a given period (leakspeed), an alert is sent through the LAPI, and a decision and sent to my custom bouncer. It is a python app that creates a GCP Cloud Armor rule, based on the IP address, TLS JA3 fingerprint or TLS JA4 fingerprint that reached the threshold.

My problem is that the GCP Cloud Armor rule that are automatically created by Crowdsec aim the bots but also legit customers that want to navigate through the website. I guess that several customers or bot can show the same fingerprint.

I would like to refine my scenarios so that they target only the bots.

Have one you already faced this problem? If yes, how did you succeed in fixing the situation? Did you correlate other inputs to be more precise in the detection?

Thanks a lot for your feedbacks :)


r/CrowdSec • • Jul 16 '26

general Crowdsec on PFsense

1 Upvotes

Subject: CrowdSec 1.7.8 on pfSense 26.03.1: Log Processor and LAPI failing to stay started

Hi everyone,

I recently installed CrowdSec 1.7.8 on pfSense 26.03.1 using the installation script (which completed successfully).

However, I'm running into an issue: while the CrowdSec Firewall Remediation service runs perfectly, both the CrowdSec Log Processor and the Local API (LAPI) service keep stopping and will not stay started.

Yes. I know Crowdsec isn't officially supported by Netgate.

Has anyone encountered this issue or have any ideas on how to troubleshoot this?

Thanks in advance!


r/CrowdSec • • 12d ago

bug Authentik Traffic Always Flagged

1 Upvotes

Hi, I'm having lots of troubles working with CrowdSec + Bunkerweb.

I'm using the bunkerweb-bouncer and the crowdsec-bouncer and every time I navigate to the /api/v3 urls on Authentik I'm getting banned.

I've tried disabling all the limiting and bad behaviour on Bunkerweb but CrowdSec always picks up on my legitimate traffic on those endpoints and bans me.

Is there anyone running the same or similar setup and knows how to fix this behaviour? Is my first time working with CrowdSec and I'm getting banned more often than actual attackers.

P.S. CrowdSec is running bare metal and communicating with Bunkerweb through the API.


r/CrowdSec • • May 08 '26

general Crowdsec Dashboard install on Unraid

0 Upvotes

Hey guys - quick question.

Edit/Update: I'm leaving my original post/question below as-is, but in a moment of clarity, I realized what the directions were probably saying was that 99:99 wasn't key:variable but was <crowdsec_value>:<crowdsec-dashboard value>.
I had gotten it working earlier by manually changing permissions with chmod on the crowdsec.db file but after a restart of my containers a few days later the permissions returned to what it was before and dashboard was no longer able to read crowdsec.db.
Resolution:
In the crowdsec container I set key:variable to UID:99, GID:98.
The crowdsec-dashboard container has MUID:99, MGID:98 so it looks like these variables map between the containers like:
crowdsec UID = crowdsec-dashboard MUID, value is 99 for both.
crowdsec GID = crowdsec-dashboard MGID, value is 98 for both.

Once I updated crowdsec with UID:99, GID:98, crowdsec-dashboard can now read crowdsec.db again.

Original Post where my understanding of the directions wasn't correct:
I'm new to crowdsec and just got it up and running on Unraid. Now I'm following up with the metabase crowdsec-dashboard container install on Unraid.

Under "Additional Requirements" it states:

Add the following to your Crowdsec container as enviroment variables to give the dashboard appropriate permisions to read data:
UID: 99:99
GID: 98:98

Is that format in <variable name>: <key>:<value> ?

So I would go back to the crowdsec config and add this variable as shown in my screenshot and repeat for GID: 98:98, right? It just seemed a bit strange adding a numeric key so just wanted to double-check.


r/CrowdSec • • Mar 11 '25

general The CrowdSec New Enterprise Plan - Question

1 Upvotes

Hi I am a retail (individual) user of CrowdSec. I have installed the CrowdSec Engine on three of my computers. I have got a question on this new CrowdSec Enterprise Plan ($31/month) which seems to be good and also affordable. I am wondering (from a private/retail user's point of view), this $31/month is per device or I could benefit from this plan for all the PCs that I have installed the CrowdSec engine on. Where I am coming from is it says $31/month per CrowSec engine per server but I don't have a server. Many thanks in advance for a reply.


r/CrowdSec • • May 13 '24

Host a custom blocklist based on IP's found in my network

2 Upvotes

I have equipped my proxy server with a Crowssec security engine. It is enrolled and visible on my dashboard. The next step is to install a Remediation Component. My preference is for a 'Blocklist mirror'. I would like to create a custom blocklist based on the findings of the newly installed Crowssec Security engine. Can I host the Remediation Component, the blocklist mirror, independently of my security engine? In the form of a Docker container or something similar? Can this Remediation Component serve only the blocklist with IPs originating from my Crowssec Security engine on my proxy server?


r/CrowdSec • • Apr 26 '26

general Is my IP just not getting scanned?

Thumbnail
gallery
0 Upvotes

Hello all,

I'm running Crowdsec to protect my exposed Caddy reverse proxy. Caddy image is a special build for use with Crowdsec & Cloudflare (serfriz/caddy-cloudflare-crowdsec).

The screenshots show what I'm seeing and the 2 blocklists I'm using. I also use the following collections within crowdsec:

  • crowdsecurity/caddy

  • crowdsecurity/http-cve

  • LePresidente/jellyfin

What's odd is you can see Crowdsec is bouncing these regular CENSYS scans, but nothing else. Also, I tested spam logging into my jellyfin while on VPN and the activity was successfully blocked as it detected a brute-force attempt. ALSO, I did an external scan while on VPN and Crowdsec also detected and blocked that.

I find it hard very hard to believe that my IP just doesn't get scanned but that's the only thing I can think of as to why I'm not seeing anything. Any help or input from the community? Feel like I must be missing something.


r/CrowdSec • • Mar 09 '24

Crowdsec is having a hard time identifying bad actors on real work attack scenarios

6 Upvotes

Recently JetBrains' Teamcity, a popular CI/CD web service was affected by CVE-2024-27198 and CVE-2024-27199, which were publicly disclosed on March 4th. It's the 3rd critical vulnerability since October 2023, but it's the first one for which the POC was made public less than 24hrs after the patches have been issued. To this day, LeakIX says more than 1500 servers all around the world are affected.

I am a gamedev hobbyist and I got Teamcity running for several years exposed to the entire internet with no fuss until that dreaded month of October 2023 where I finally got pwnd. After recovering, I decided to jump on the Crowdsec bandwagon as it was extremely praised all around.

So I got it installed, alongside a bunch of secondary mitigation measures because we never know.

When the last vulnerability hit, I only patched two days later, and so I could monitor extensively all the targeted attacks. I cross-referenced IP in order to assess how sharp would be Crowdsec in the case of a very recent, highly critical and very targeted vulnerability exploit.

Here are the IPs caught by CrowdSec blocklists (I'm using here 3 BLs from the free version: Firehol BotScout, Firehol cruzit.com and Free proxies list, as well as the default 59 attack scenarios)

  • 161.35.155.246

  • 167.71.185.75

  • 188.166.87.88

  • 170.130.75.10

  • 199.45.154.17

  • 199.45.155.33

  • 199.45.155.48

Here are the IPs of the (bad) actors that attempted to exploit CVE-2024-27198:

  • 185.174.137.26

  • 103.253.73.99

  • 146.0.228.66

Here are the IPs of the bad actors that attempted to deploy malware:

There is no match between CrowdSec IPs and the far more dangerous ones actively exploiting the vulnerability.

I can't recommend having only CrowdSec as your main line of defense. Consider combining with Fail2ban (does a great job at geoip banning!), WAF with ACLs, etc.