I am not able to connect my Filezilla or Putty with Google Cloud through SSH
Chirayu Bhatt
I followed the steps mentioned here: https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#edit-ssh-metadata and here: https://cloud.google.com/compute/docs/instances/connecting-advanced#thirdpartytools
1) I create the Key pair using puttygen
2) I copied the public key using my GCE email id as Key Comment at puttygen
3) I pasted the public key to the Google Instance Metadata->SSH keys->Add new
4) I saved the private key and assigned to SSH->Auth section
5) Now i am trying to connect it through putty
In Putty I get "Disconnected: No supported authentication methods available (server sent: publickey)" error with "server refused our key".
I went through all documentations, but no success. Is there anything I need to to with IAM?
In Filezilla I get the error: "Disconnected: No supported authentication methods available (server sent: publickey)".
is there anything to do with IAM role. I checked and tried to follow the google console help article but no success.
regards,
Yui (Google Cloud Support)
Hi
Since you are getting errors on two different third party applications, I suspect the issue is more related to your target VM.
Could you please try the following:
1.On Putty key generator, please generate the key.
2.After at "key comment", put a username for example “chirayu”. Save the private key.
3.Now in your target instance. [Compute engine> Vm name>edit] At “You have 0 SSH keys”, add your key. Once you paste the entire key, you will see that the username will populate on the left (chirayu).
4.Now go back to Putty, put the external IP address in Host name. At connection> SSH>Auth> choose your .ppk file you created before + check Allow agent forwarding. Open.
5. A new window will open to allow you to connect with your username (chirayu).
If that fails, please use the ssh browser, to log in to your VM, and perform the following
1.sudo -s
2.cd /home/chirayu/.ssh
>navigate to folder to check the authorized_keys file
3.cat authorized_keys
>make sure that the public key entered corresponds to step 3 above.
Let me know.