• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Xmlrpc attack problem

I can confirm that the Wordpress app will cause users to be blocked by Fail2Ban. That is mainly for the very high frequency that this app connects to the site and transmits more or less "empty" POSTs to it or repeatedly requests the same files from the Wordpress installation. It is more an issue of the app than an issue of the jail. The app has no reason to continuously communicate with the server and creates a lot of unnecessary load. It's been that way for years.

To disable xmlrpc.php for good in Wordpress, insert these lines into the .htaccess file in the Wordpress directory:
<Files xmlrpc.php>
order deny,allow
deny from all
</Files>

Also, look at the "Security" button of the Wordpress Toolkit in Plesk. You can also disable XMLRPC in there.
 
Hello

As @Peter Debik correctly explains, you can control this with .htaccess (deny/allow all or deny/allow only for ips).
If you don't want to do it manually or want a more general blocking per country, you can use our plugin: Deny-country Extension, it also allows limiting the attack on wp- login.php (something common Unfortunately, in our case for example, it's easy to limit access to spain the wp-login and unlock it for client that need access to other countries)
 
Back
Top