• 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 ClamAV install settings on Plesk

Zoo3

Regular Pleskian
I installed ClamAV and I am able to run it by the command line. I use an application called Nextcloud, which uses ClamAV.

When the application executes ClamAV, it causes a permission error. "/var/run/clamd.scan/clamd.sock".
I have specified the user as "root" in the scan.conf of ClamAV. I have given the Plesk user root privileges with the VISUDO command. I can not resolve this error even if I specify the user as Plesk user in scan.conf. In the meantime I am changing the owner and group of /var/run/clamd.scan/ in turn "PLESK-USER : psaserv" and I am working somehow. However, this unintentionally unintentionally returns to "clamupdate: virrusgroup".
Even if I specified the user as PLESK-USER in scan.conf, I did not solve it.

There is no problem in executing the clamdscan command in the normal state. There is a problem with ClamAV execution by Nextcloud.

How should I configure Plesk permanently and stably to use ClamAV in Nextcloud?
 
Back
Top