https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNTEyIiwiaGFzaCI6ImEwNzZhNjIwLTQ5NTItNDVlNS1iMWEzLTRlZjA0MGFhMTlhOSJ9
1-800-691-1991 | 9am - 8pm ET
EN

User authentication failed

Challenge

When trying to add a Linux server to the Veeam Backup & Replication console, you get the following error:

Failed to login to "xxx.xx.xx.x" by SSH, port 22, user "root"
elevateToRoot False, autoSudo False
User authentication failed

However, it is possible to log on to this server with the same credentials using an SSH client.

Cause

The configuration of your SSH server does not allow using tunnelled clear text passwords.

Solution

  1. Open the SSHD config file (usually, /etc/ssh/sshd_config) on the Linux server.

  2. Find the PasswordAuthentication parameter and set its value to “yes”.

  3. Restart SSHD on the Linux server (usually, /etc/init.d/sshd restart).

  4. Try adding the server to the console again.

More information

Another solution is to use  the Identity/Pubkey authentication method.
https://helpcenter.veeam.com/docs/backup/vsphere/credentials_manager_linux_pubkey.html?ver=95u4 
KB ID:
1512
Product:
Veeam Backup & Replication
Version:
5.x, 6.x, 7.x, 8.x, 9.x
Published:
2012-02-08
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later