Google putty connect "Disabled: no authentication methods available (server sent: publishing)

Question

I try to connect to my Google Compute Engine server using PuTTy (I also tried other alternatives), but when I do this, I get the error message "Disconnected: no authentication methods available (server sent: publication)

The google server came without a username and password, only to automatically log into your terminal.

Answer 1

I had PuTTY, and one day I got this error.

Solution . I revised the name of the folder path containing my certificates (private keys), and this caused Pageant to lose the certificate information and therefore was empty.

As soon as I installed the certificate in Projectant again, Putty started working again.

Answer 2

Enable Password Authentication

By default, you need to use the keys for ssh on a computer with a Google computer, but you can enable password authentication if you do not need this level of security.

Tip. . Use the Open option in the SSH browser window from the cloud console to access the machine. Then switch to the root user using sudo su - root to change the settings below.

• Edit the file /etc/ssh/sshd_config .
• Change PasswordAuthentication and ChallengeResponseAuthentication to yes .
• Restart ssh /etc/init.d/ssh restart .

Answer 3

You need to use the SSH key to enter your instance.

The GCE documentation explains the process here .

Answer 4

Please follow this guide: https://gist.github.com/feczo/7282a6e00181fde4281b with pictures.

In short:

Using Puttygen, click Generate, move the mouse as directed and wait

• Enter your username

• Enter your password

• Save Private Key

Copy the entire content of the "Public key to paste into the OpenSSH authorized_keys file." Be sure to copy each character from the very beginning to the very end!

Go to the Create Instances page in the Google Cloud Platform console, and in the advanced settings link, paste the contents of your public key.

Note the IP address of the instance after it has completed. Open the putty, from the left menu go to Connection / SSH / Auth and locate the key file that was saved.

In the menu on the left, select "Connection / data" and specify the same username

• Enter the IP address of your instance
• name the connection below the saved sessions as "GCE", click "Save"
• double-click the "GCE" entry you just created.
• accept host id

Now log in with the password you specified earlier and run sudo su - and you're all set up.

Answer 5

I had the same problem and I just got it!

Assuming you have already gone and created your private / public key, your public key has been added on the remote server ... enter [e-mail] and THEN go to Connection → SSH → Auth and click Browse to find your private key. Once you select, it will fill in the input field. After that press OPEN ...

So, here it is important to specify the order ... make sure that you first enter the parameters for the host, and then find your private key.

Answer 6

I got this error because I forgot to add my username behind the key in the GCE metadata section. For example, you should add an entry to the metadata section, which looks like this:

 sshKeys username:key 

I forgot the username: part username: and so when I tried to log in with this username, I got an error from the supported auth methods.

Or, to completely disable the ssh key condition , check out my other answer .

Answer 7

Apparently running sudo chmod -R a+rw in your home folder makes this happen as well.

Answer 8

PasswordAuthentication and ChallengeResponseAuthentication are set to NO in rhel7 by default.

Change them to NO and restart sshd.

Answer 9

If the private key was generated using ssh-keygen on Linux, it needs to be converted using puttygen because Putty does not support openssh keys.

Launch puttygen and click the "Conversions - Import" button, then click "Browse" and select the private key generated by openssh, then click "Save Private Key".

Use the new key to connect.