Dr.Web (R) Updater

[Blondie63]

I've Plesk Panel 10.3.1 and i'm Admin

I receive many many email like this:

ERROR: Dr.Web (R) Updater: remote host update.msk7.drweb.com closed connection variant () !
ERROR: Dr.Web (R) Updater: remote host update.msk7.drweb.com closed connection variant () !
ERROR: Dr.Web (R) Updater: remote host update.msk7.drweb.com closed connection variant () !
ERROR: Dr.Web (R) Updater: cannot download timestamp !
ERROR: Dr.Web (R) Updater: failed to download new/updated files from http://update.msk7.drweb.com/unix/500 !
ERROR: Dr.Web (R) Updater: remote host update.msk.drweb.com closed connection variant () !
ERROR: Dr.Web (R) Updater: remote host update.msk.drweb.com closed connection variant () !

and this:

ERROR: Dr.Web (R) Updater: remote host update.us.drweb.com closed connection variant () !

Someone know why? and how to fix it ?

Thanks

Mauro

 

[IgorG]

Check that these hostnames are accessible from your server at least. And I think that it is DrWeb related problems and you may contact their support or look at their forum.

 

[JasperV]

Check that these hostnames are accessible from your server at least. And I think that it is DrWeb related problems and you may contact their support or look at their forum.

In my situation the hostnames are accesible and therefor I contacted DrWeb Support about this matter. This is what they say:

Request GUV8-0919 / Action 4300564
Date / Time 14.03 01:03:43
Who Karl Schmitz
Action, Request status Add comment, User response needed
Data
Dear Jasper,

sorry for having you wait so long. After consulting one of my colleagues, it turned out that we made a change to our update servers.
The change affects users of the Plesk-specific variants of Dr.Web products (like you) by denying them updates.

Some details about the change:
* Installed Dr.Web updater scripts have to authenticate themself with the MD5 hash of their Dr.Web license key, which the update server validates against our license DB.
* The Plesk-specific variants of Dr.Web products have a special plesk.key and no regular drweb32.key. Thus, your updater can't present a proper MD5 hash and gets denied.

Anyway, as it's about a Plesk-specific variant, I am obligated to request you to forward this issue to Parallel's Plesk support.

Kind regards,

Karl Schmitz
Sales Engineer
Doctor Web Deutschland GmbH