• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question Using ClamAV with Plesk

Zoo3

Regular Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
18.0.45
I'm running an online storage management application called Nextcloud. And I am also running ClamAV. In Nextcloud, when ClamAV (via the Nextcloud application) detects a file, it outputs a large number of "no file" errors. I have been trying to find the cause in several places but have not been able to find it at all.

-> ClamAV antivirus standalone installation is not supported by Plesk.

What does this mean? I have installed clamav with yum and run it as a daemon. For example, when I use clamdscan to scan directories and files, it does not output any errors.
So would the problem be NC's ClamAV connection app?
In addition to real-time scanning, NC seems to have a cron that is triggered every 5 minutes and the ClamAV connection app also seems to be running some functionality. At this time, the error in question outputs about 100 errors.

I created a subdomain in Plesk and installed and verified a completely new Nextcloud. The same error occurred with the new NC.
Is this due to "not supporting stand-alone installation"? Is this simply a problem with the ClamAV connection app in the Plesk environment?
If it is a Plesk specific issue, is there anything I can advise the author of the app?
 
Back
Top