Comments - MONyog ssh authentication using key

7 years, 10 months ago Sibin AS

Please ensure that you are entering the IP address of the machine where the SSH server is running in the ‘SSH host’ field and enter the SSH username to access the SSH server (not of the MySQL server) in the ‘SSH username’ field.

This is an authentication error. Please make sure that you have entered the correct SSH keys with the required file permission to the key file. We have our FAQ which says how to resolve this issue, here >>

7 years, 10 months ago palash harchandani

I have checked the permissions and also checked if all the parameters are correct. but still i am getting the same error!!

7 years, 10 months ago Sibin AS

Please follow the below steps:

1) Edit PasswordAuthentication line in /etc/ssh/sshd_config to "PasswordAuthentication no" to force RSA auth

2) Change the path for the file “authorized_keys” to some other directory like “/etc/ssh/user/authorized_keys”

3) Make the corresponding change in the “sshd_config” file, and change the value for “AuthorizedKeysFile” to AuthorizedKeysFile = /etc/ssh/user/authorized_keys

4) Restart sshd service (sudo service sshd restart)

Please tell us if this fixed the issue.

7 years, 10 months ago palash harchandani

This doesnt solve the problem!!

7 years, 10 months ago Sibin AS

Can you please tell what error do you get now.

7 years, 10 months ago palash harchandani

Failed to connect to SFTP: SshConnectAuthorize: Could not get private key -- Access denied. Authentication that can continue: publickey,gssapi-keyex,gssapi-with-mic,password

7 years, 9 months ago palash harchandani

The problem got solved...Thanks!!

7 years, 3 months ago Saksham Ahuja

Could you tell us what was the solution to the issue here?

7 years, 9 months ago Sibin AS

Just curious to know what was the issue and how did you get it solved.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.