• 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.

Question New "Gutenberg" Wordpress text editor triggers Fail2Ban?

Bitpalast

Plesk addicted!
Plesk Guru
We are getting customer reports that the new Gutenberg Wordpress text editor triggers a Fail2Ban IP address block soon after using it. However, we have not yet had the opportunity to reproduce this or test whether this is caused by the ModSecurity jail or the Wordpress jail. Has anyone else experienced or heard of similar issues?
 
I am only aware of this part:
"
  • Additionally, if Fail2Ban is enabled on the server, your client IP quickly gets banned by the Apache jail for accessing restricted elements while you are just trying to edit articles."
Not sure if it is caused by wp-includes security.
 
We are getting more reports from customers now as Wordpress promotes testing the "Gutenberg" editor as a plugin before they integrate it into their packages as their default.

Personally, I think that the issue is caused by the asynchronous behavior of Gutenberg that stores everything a user types or changes every n seconds, repeatedly requesting the same URLs within a short period of time and for that reason behaving similar to a DoS attack. According to Gutenberg triggers Fail2Ban Wordpress jails in Plesk · Issue #9933 · WordPress/gutenberg the developers don't really know what to do about it at the moment.
 
Back
Top