Input Would you use a turnkey Plesk + CrowdSec extension? (gauging interest)

[BrunoA]

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.

 

[presswizards]

I recently installed it via SSH and it's working great. Most of my client sites are behind Cloudflare, and I have mod_security enabled and some customized fail2ban bad-bot and WordPress rules, but one server has a large mix of older client sites, and kept getting hammered by bots still. Crowdsec is awesome, and was pretty easy to install and configure. It's blocking a ton of IPs based on the community lists, plus direct blocks based on the collections.

Then I was looking at cscli metrics and cscli decisions list, and decided to use Claude and cscli to create a little mini dashboard in PHP, separate from whatever the Crowdsec console provides, because I want something tighter and in one place, screenshot attached.

It'd be great to have a native Plesk extension, but I wouldn't pay for it unless it did something beyond the basics. I actually don't want per-domain controls, I like it to be server-wide as a strong foundational layer that I don't have to manage much.