• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Question How to make fail2ban logpath aware of logs in Plesk managed domains

Zoo3

Regular Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
18.0.48
I'm using Nextcloud and want to set its logfile to fail2ban's logpath. But when I specify the Nextcloud log(/var/www/vhosts/MYACCOUT/nextcloud/data/nextcloud.log), fail2ban gets failed.
It seems that fail2ban can only be specified in /var/log or some other area. For example, I can't specify "/var/www/vhosts/MYACCOUT/logs/test.log" or "/var/www/vhosts/MYACCOUT/test.log" as logpath to start fail2ban.

How can I specify a directory in Plesk management to fail2ban?
 
I had forgotten about SELINUX. So it seems to be blocked. If I Permissive or disable, fail2ban works.
I mechanically set SELINUX according to the official manual.

The following is directed by it
Code:
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/nextcloud/data(/.*)?'

This specifies all files under the data directory, right?
So I tried deleting only the nextcloud.log setting in the data directory.

Code:
semanage fcontext -d '/var/www/html/nextcloud/data/nextcloud.log'
Then the error message "not defined" will appear. Of course, path is replaced with my correct information.

I want to protect the data directory itself with selinux, but only open the log file. How can I do this?
 
Back
Top