• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved Could you please explain changes to the Fail2Ban jails in 18.0.63 in more detail?

Bitpalast

Plesk addicted!
Plesk Guru
Server operating system version
Alma 8 and 9
Plesk version and microupdate number
18.0.62, 18.0.63
According to another post, the "recidive" jail has been replaced by two new jails "plesk-one-week-ban.conf" and "plesk-permanent-ban.conf". We're using custom software and definitions that partly rely on the "recidive" chain and .conf. I'd like to know more what the two new confs do, whether recidive is kept and how they play together.
 
[...], the "recidive" jail has been replaced by two new jails "plesk-one-week-ban.conf" and "plesk-permanent-ban.conf".
That's incorrect. The recidive jail hasn't been replaced. Two new jails have been introduced: plesk-one-week-ban and plesk-permanent-ban

We're using custom software and definitions that partly rely on the "recidive" chain and .conf. I'd like to know more what the two new confs do, whether recidive is kept and how they play together.
The two new jails are for adding manual IP bans via the Plesk GUI. There have been no modifications to recidive jail or to the way recidive jail functions.
 
Back
Top