Tune CrowdSec http-probing capacity to 20 via authored mount #53
Loading…
Reference in a new issue
No description provided.
Delete branch "crowdsec-http-probing-tuning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
crowdsecurity/http-probingscenario in git (capacity: 10 -> 20) and mount it read-only over the installed hub copy on the Droplet, following the acquis.d precedent so hub upgrades never clobber it.fj(forgejo-cli) probes two PR-template dirs x three extensions on every PR command, and Forgejo 404s each miss: 11 requests in ~1s, one over the hub default's capacity of 10. CrowdSec read that sweep as an attack scan and banned the home IP for four hours, denying every Pangolin resource plus the fleet agents' auth endpoints, which all egress from the same address.leakspeed: 10sbarely refills the bucket.Deployment
The live edge is already fixed (ban removed 2026-10-14, scenario tuned in place and reloaded, recovery verified: dashboard and forge 200 from home, all three sites reconnected). This PR converges git with the running state; after merge,
make sync && make up dropletapplies the authored mount and the container state matches the repo.