Question Plesk firewall - CrowdSec iptables interaction

[andg]

Server operating system version

Debian 10

Plesk version and microupdate number

Plesk Obsidian 18.0.68 Update #2

Hi,
after successfully configuring crowdsec in a bare metal server I tested it with Plesk.
Turned off fail2ban, installed crowdsec with iptables bouncer and created a few custom rules.
All seem good except that if I update Plesk firewall rules and apply the update CrowdSec rules in iptables are no longer enforced.
Listing iptables rules
Before:

Chain CROWDSEC_CHAIN (1 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere             match-set crowdsec-blacklists-1 src
DROP       all  --  anywhere             anywhere             match-set crowdsec-blacklists-0 src

After a plesk firewall rule got updated

Chain CROWDSEC_CHAIN (0 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere             match-set crowdsec-blacklists-1 src
DROP       all  --  anywhere             anywhere             match-set crowdsec-blacklists-0 src

So as you can see it gets 0 references. Doing a systemctl restart crowdsec-firewall-bouncer fixes the problem.
Would it be possible to trigger a script after the firewall is updated? Or to integrate them better in other ways?
Also I've yet to test what happens after a server restart but think should be ok. Will update about it!
Thanks!

 

[Kaspar]

Would it be possible to trigger a script after the firewall is updated?

See: Question - Disable FTP on single ip address