• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue ClamAV install settings on Plesk

Moosewala

New 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 https://100001.onl/ https://1921681254.mx/.

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