- Veeam Support Knowledge Base
- Secure channel communications stop working after disabling TLS 1.0/1.1
Secure channel communications stop working after disabling TLS 1.0/1.1
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
The following error will be listed in the Svc.VeeamBackup.log log file and the pop-up error window.
The client and server cannot communicate, because they do not possess a common algorithm.Cause
Solution
The following registry keys need to be added on machines where TLS 1.0/1.1 has been disabled to force the usage of TLS 1.2.
Key Location: HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
Value Name: SchUseStrongCrypto
Value Type: DWORD (32-bit) Value
Value Data: 1
Key Location: HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
Value Name: SystemDefaultTlsVersions
Value Type: DWORD (32-bit) Value
Value Data: 1
Key Location: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
Value Name: SchUseStrongCrypto
Value Type: DWORD (32-bit) Value
Value Data: 1
Key Location: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
Value Name: SystemDefaultTlsVersions
Value Type: DWORD (32-bit) Value
Value Data: 1
A .reg file is provided by Microsoft that will set these keys to their safest values:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-security-via-the-windows-registry
More Information
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls
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.
Oops! Something went wrong.
Please try again later.
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.