• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

What are these fail2Ban jails?

K

Kroptokin

Regular Pleskian
I am configuring fail2Ban (brilliant idea to include it in the Panel).

I am wondering what the implication is of activating it for these services:

plesk-apache
plesk-apache-badbot
plesk-horde
recidive

I am not sure what these services are. Also surely if we apply it to plesk-apache that would block Apache? Or is this something different?

Thanks

--Justin Wyllie
 
You must log in or register to reply here.

Similar threads

Azurel
Input AlmaLinux8to9 upgrade leaves Plesk in broken state with insufficient service checks and recovery guidance
Replies
2
Views
1K
Azurel
Azurel
I
Forwarded to devs Postfix fail2ban filter misses authentication failures
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Azurel
Resolved ModSecurity shown as "On" in Plesk GUI but runtime is "Disabled" and modsec_audit.log stays empty
Replies
2
Views
983
Azurel
Azurel
Daveo
Question Server accessible internally only
Replies
2
Views
2K
Daveo
Daveo
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
3K
iainh
I
Back
Top