Clamav database update blocked by CDN

Hello,

since a few days i get an error mail every day because the automatic clamav update is no longer working:

ERROR: Database update process failed: Forbidden; Blocked by CDN ERROR: Update failed

Is there a new repository i should use or will there be an update to fix this?


The error seems to be because CWP7 is using an old and outdated clam AV -> see attachment terminal response:

Code: [Select]

[root@srv1 ~]# freshclam
ClamAV update process started at Tue Oct  7 16:22:33 2025
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.103.11 Recommended version: 1.0.9
DON'T PANIC! Read https://docs.clamav.net/manual/Installing.html
WARNING: FreshClam previously received error code 429 or 403 from the ClamAV Content Delivery Network (CDN).
This means that you have been rate limited or blocked by the CDN.
 1. Verify that you're running a supported ClamAV version.
    See https://docs.clamav.net/faq/faq-eol.html for details.
 2. Run FreshClam no more than once an hour to check for updates.
    FreshClam should check DNS first to see if an update is needed.
 3. If you have more than 10 hosts on your network attempting to download,
    it is recommended that you set up a private mirror on your network using
    cvdupdate (https://pypi.org/project/cvdupdate/) to save bandwidth on the
    CDN and your own network.
 4. Please do not open a ticket asking for an exemption from the rate limit,
    it will not be granted.
WARNING: You are still on cool-down until after: 2025-10-08 16:12:35


Thanks

What OS are you running? Under AlmaLinux 8 with CWP, I have:

Code: [Select]

root@srv1]# clamd --version
ClamAV 1.4.3/27785/Tue Oct  7 02:40:12 2025

i am still on centos 7

Having an EOL operating system (over the one year mark), you can expect to see any updates fizzle out and support for it dry up. Have you at least switched your repositories to the "vault" URLs so you can at least scrape out the last updates? Have you considered a CWP Migration? It works fairly well and offers a fairly painless migration path to AlmaLinux 8 so you can get to a more supported OS.

https://www.alphagnu.com/topic/562-fix-centos-8-repo-due-to-eol-could-not-retrieve-mirrorlist/

AL9 shows the same 1.4.3 version as AL8:

Code: [Select]

# clamd --version
ClamAV 1.4.3/27778/Tue Sep 30 08:29:52 2025
And @oversser is correct, there are No, None, Zilch, Zero, Nadda more updates for CentOS 7 since it's past EOL, and has been moved to the archive vault.

You need to update the server to AL8, if you want updates.

AL9 shows the same 1.4.3 version as AL8:

Code: [Select]

# clamd --version
ClamAV 1.4.3/27778/Tue Sep 30 08:29:52 2025
And @oversser is correct, there are No, None, Zilch, Zero, Nadda more updates for CentOS 7 since it's past EOL, and has been moved to the archive vault.

You need to update the server to AL8, if you want updates.

Ok thanks, yes i wanted to switch over to AL8 using this Elevate script but never did it till now.

I think it is really time to do it, i was worried if everything will work but now as a lot time passed by and you said it is working flawless i think it is the time to update.

Thanks a lot

ELevate is not a recommended upgrade path; you will likely introduce issues into the new system (Sandeep [a CWP dev] advises against it). Better to bring up a new AlmaLinux 8 system and use the CWP Migration module to transfer accounts. That's the route I chose and so I have a fresh system with very little cruft moved over from the old system. Fresh 'n shiny!
https://www.alphagnu.com/topic/578-does-it-possible-to-migrating-from-centos7-to-almalinux9-same-server-without-installing-to-new-server/