• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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