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

Issue Fail2Ban blocking Web_user - No Xferlog

Jayson

Basic Pleskian
Hello,

I recently upgraded to 12.5 and have enabled Fail2Ban. I'm getting complaints that it keeps blocking a customer trying to use his configured Web_User account. I'd rather not whitelist his IP and wanted to check xferlog for reasons for blocking. Under his domain logs the last entry I see in xferlog_regular.processed was from October and it appears like this for other domains which should have ftp statistics.

I found the KB https://kb.plesk.com/en/127106 and although /etc/proftpd.conf has
"TransferLog /var/log/plesk/xferlog" those files are 0 bytes.

/var/log/plesk
-rw-r-----. 1 root root 0 Nov 9 03:37 xferlog
-rw-r-----. 1 root root 0 Oct 15 03:08 xferlog.processed

Under the domain statistics I see the old xferlog files,

/customerdomain/statistics/logs
-rw-r--r--. 2 root root 0 Oct 14 03:51 xferlog_regular
-rw-r--r--. 2 root root 14177642 Oct 14 03:51 xferlog_regular.processed

Thanks,
 
Back
Top