How can I fix the error: You are running an out of date version of ClamAV / FreshClam?

This error means that you are using an operating system that is end of life so ClamAV is no longer providing signature updates for that OS. These OS include CentOS 7.x/CloudLinux 7.x/RedHat Enterprise Linux 7.x/Debian 10.x/Ubuntu 20.04 running ClamAV 0.103.0. ClamAV stopped providing anti-virus signature downloads for operating systems on Sept 14, 2025. See here for more information.

 

Signature Log

Upgrade Your Operating System

To fix this issue you should upgrade/migrate your server to a supported OS. Centos 7 OS can perform an in place upgrade to AlmaLinux 8, Ubuntu/Debian OS can perform a dist-upgrade to a new OS version, all other OS can use the Plesk migrator to migrate sites over to a server running a supported OS.

Centos 7 users doing an in place upgrade will also have to perform additional tasks after upgrading. See here for more information.

 

 

  • freshclam, end of life
  • 0 Utilisateurs l'ont trouvée utile
Cette réponse était-elle pertinente?

Articles connexes

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....