Facebook
Twitter- Server operating system version
- Ubuntu 24.04.4 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.78.3
There are recurring threads here about running CrowdSec on Plesk, and about brute-force on the panel/webmail that Fail2Ban and the stock tools don't fully cover.
I've built a working Plesk + CrowdSec integration: custom parsers for the Plesk panel (8443/8880) and Roundcube webmail, plus the bouncer and auto-configuration. It's been running in production for ~2 months on a 34-domain server — ~5,000 attacks blocked (including ~2,150 .env and ~1,650 .git credential-theft probes), zero compromised sites.
Before deciding whether to release it as a proper extension, I'd like to gauge real interest. Would you use a turnkey Plesk + CrowdSec extension? Vote below, and feel free to comment what would matter most to you — per-domain controls, a managed blocklist, panel/webmail protection, pricing expectations, etc.
I've built a working Plesk + CrowdSec integration: custom parsers for the Plesk panel (8443/8880) and Roundcube webmail, plus the bouncer and auto-configuration. It's been running in production for ~2 months on a 34-domain server — ~5,000 attacks blocked (including ~2,150 .env and ~1,650 .git credential-theft probes), zero compromised sites.
Before deciding whether to release it as a proper extension, I'd like to gauge real interest. Would you use a turnkey Plesk + CrowdSec extension? Vote below, and feel free to comment what would matter most to you — per-domain controls, a managed blocklist, panel/webmail protection, pricing expectations, etc.
