"The request was aborted: Could not create SSL/TLS secure channel" after installing Windows Updates
| KB ID: | 2164 |
| Product: | Veeam Backup & Replication |
| Version: | All |
| Published: | 2016-09-27 |
| Last Modified: | 2020-08-13 |
| Languages: | FR |
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
Challenge
After installing the security Windows Updates released in September or October 2016, outgoing HTTPS connections from Veeam server to vCenter and NetApp storages may fail with
The request was aborted: Could not create SSL/TLS secure channel.
Any other HTTPS connections may be affected as well.
The request was aborted: Could not create SSL/TLS secure channel.
Any other HTTPS connections may be affected as well.
Cause
After installing one or more of the following security updates:
2012 R2 and Windows 8
KB3185331
KB3188743
KB3174644
2008 R2 and Windows 7
KB3185278
KB3185330
KB3192391
KB3175024
KB3172605
Please note that Windows Monthly Quality Rollups may replace the aforementioned updates. For more information consult Microsoft Update Catalog.
If the public key length is shorter than 2048 bytes (e.g. RSA 512), Windows may cancel the HTTPS connection.
2012 R2 and Windows 8
KB3185331
KB3188743
KB3174644
2008 R2 and Windows 7
KB3185278
KB3185330
KB3192391
KB3175024
KB3172605
Please note that Windows Monthly Quality Rollups may replace the aforementioned updates. For more information consult Microsoft Update Catalog.
If the public key length is shorter than 2048 bytes (e.g. RSA 512), Windows may cancel the HTTPS connection.
Solution
To fully resolve the problem, regenerate vCenter or NetApp certificates so that the public key length is at least 2048 bit.
Please note that KB3172605 update causes issues with SHA-1 certificates even with the longer public key. For that one, you may want to generate the SHA-2 certificate.
As a workaround, you can uninstall the updates if you have them installed.
Please note that KB3172605 update causes issues with SHA-1 certificates even with the longer public key. For that one, you may want to generate the SHA-2 certificate.
As a workaround, you can uninstall the updates if you have them installed.
More information
Microsoft Security Bulletin Summary for September 2016 https://technet.microsoft.com/en-us/library/security/ms16-sep.aspx
Vmware docs: Create Self-Signed Certificates
NetApp docs: security certificate create
Vmware docs: Create Self-Signed Certificates
NetApp docs: security certificate create
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.