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

No i can activate Jails apache in fail2ban

RubénN

New Pleskian
f2bmng failed: ERROR NOK: ('plesk-apache',)
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR NOK: (13, 'Permission denied')
ERROR:f2bmng:Command '['/usr/bin/fail2ban-client', 'reload', 'plesk-apache']' returned non-zero exit status 255
ERROR:f2bmng:Failed to reload following jails due to errors in configuration: plesk-apache

In fail2ban.log:

fail2ban.comm [31357]: WARNING Command ['set', 'plesk-apache', 'addlogpath', '/var/www/vhosts/system/domain1.tld/logs/error_log'] has failed. Received IOError(13, 'Permission denied')
fail2ban.comm [31357]: WARNING Command ['set', 'plesk-apache', 'addlogpath', '/var/www/vhosts/system/domain2.tld/logs/error_log'] has failed. Received IOError(13, 'Permission denied')
.....
 
Last edited:
What is the user your fail2ban daemon runs under? What permissions do error_log files have? Do you have selinux or anything similar enabled?
 
Back
Top