The negotiation of encryption algorithm is failed
| KB ID: | 1890 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x, 7.x, 8.x |
| Published: | 2014-05-30 |
| Last Modified: | 2020-08-13 |
Challenge
When trying to restore files from a Veeam appliance to the original location using Other OS restore, the following error is received: "The negotiation of encryption algorithm is failed"
Cause
Between Linux flavors, certain Ciphers may be enabled or disabled by default or by local policy.
Solution
8.0
Install the latest update for Veeam Backup and Replication. This enables aes128-ctr, aes192-ctr, aes256-ctr, aes192-cbc and aes256-cbc in addition to the already existing 3des-cbc, blowfish-cbc, and aes128-cbc.
A more secure Ciphers line would be:
6.x and 7.x:
Make sure that at least one of the following algorithms are included on your Ciphers line:
Install the latest update for Veeam Backup and Replication. This enables aes128-ctr, aes192-ctr, aes256-ctr, aes192-cbc and aes256-cbc in addition to the already existing 3des-cbc, blowfish-cbc, and aes128-cbc.
A more secure Ciphers line would be:
| Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes192-cbc,aes256-cbc |
6.x and 7.x:
Make sure that at least one of the following algorithms are included on your Ciphers line:
| Ciphers 3des-cbc,blowfish-cbc,aes128-cbc |
More information
If your security policy requires deleting this string, then it needs to be re-added every time you need to restore files to the original location.
| KB ID: | 1890 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x, 7.x, 8.x |
| Published: | 2014-05-30 |
| Last Modified: | 2020-08-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
