Jump to content

Failed to establish the HTTPS connection: TLS error (54)


Go to solution Solved by Patrick Sommer,

Recommended Posts

Hello Everybody, After KSC 11 installation, when going to update the KSC database repository, it's showing "Failed to establish the HTTPS connection: TLS error (54)" There was a similar problem was written in another post - KSC 11: can not update Antivirus DB with Traffic Security on There a solution given by Oleg Bykov - "Please add klserver.exe and Up2Date.exe to the Traffic Security exclusions." But i didn't understand exactly where i have to exclude those. Waiting to have solution....... Thanks in Advance Deadlock4400
Link to comment
Share on other sites

Hello Dmitry Parshutin The KSC 11.0.0.1131 was installed and the KES 11.1.1.126 and the Network agent is also latest 11. The problem is KSC database repository task is unable to download Update from Kaspersky Lab and the Screenshot is posted above reply before. As several times and several days it failed, had to use Update Utility tool and tag the update source to it for all KES and it's working. But the main thing that still the Kaspersky Update repository task unable to update KSC repository! As KSC 11.0.0.1131 is installed then where can i find the patch to fix this problem? please Thanks in Advance Deadlock4400
Link to comment
Share on other sites

  • 3 weeks later...
  • Solution
Hi guys, i dont know if i understand your problem right, but usually the problem ist, that your ksc download on https and your proxy break the tls (ssl bumping/tls-injection). There are two possibilitys, frist deaktivitact ssl-bumping for the https in the following link. 2nd alternativ change the way ksc download it, not recommanded but often in use, scroll the same link down there are the parameters. https://support.kaspersky.com/15052
Link to comment
Share on other sites

Hi, thanks for pointing to a workaround. i'm just wondering why it was no issue in ksc 10? Did it include an invisible fallback to http? btw this command creates the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\Components\34\1093\1.0.0.0\Updater DisableKLHttps Value: 1 i guess deleting it and restarting the service will undo the changes.
Link to comment
Share on other sites

Hi, thanks for pointing to a workaround. i'm just wondering why it was no issue in ksc 10? Did it include an invisible fallback to http? btw this command creates the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\Components\34\1093\1.0.0.0\Updater DisableKLHttps Value: 1 i guess deleting it and restarting the service will undo the changes.
Hello bitboy I agree with you about the "Did it include an invisible fallback to http" The command you show there about registry, if I do the DisableKHttps value to 1 then will the KSC update work? Thanks in Advance Deadlock4400
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...