Ssh – Compute Engine SSH unexpected end-of-file during FileZilla SFTP authentication

authenticationgoogle-compute-enginessh

I cannot get Filezilla to connect to my SSH instances at Google Cloud Compute Engine.

I followed the instructions for previous instances without issue, but in this case, I deleted two Ubuntu 16.04 server instances from my project so that I could recreate them with Cloud Storage Read/Write enabled.

Even after manually creating the keys and placing them in the Metadata page for my project, I cannot connect FileZilla to my instances. I get the error: "Received unexpected end-of-file from SFTP server."

I have tried both root@instance and root as my -C [USERNAME] but neither works.

Has anyone else encountered this issue? Thanks in advance!

Best Answer

There is a nice step by step configuration guide to setup Filezilla and use it on GCE here. An easy and automated way to configure the keys is by using “gcloud compute ssh”. If the keys do not exists, the tool will generate them and configure them in the project’s metadata. The keys are placed in the local “.ssh” directory

Related Solutions

Linux – SSH public/private authentication failing in Google compute engine instances

ssh -v -i .ssh/namenode.pub root@datanode1

When you specify an ssh key on the command line, it should be the private key file, not the public file. So you should reference .ssh/namenode here, not .ssh/namenode.pub.

It looks like you added the private key to ssh-add, but there's no indication in the ssh debug trace that it communicated with the ssh agent or offered the private key to the remote server. Perhaps you ran ssh in a different session (terminal window) from the ssh-add command, so that ssh didn't have access to the environment variables telling it how to access the agent.

Finally, the contents of the namenode.pub line is one long line. Make sure you copied it into the remote authorized_keys file as one long line, instead of three lines.

Ssh – Unable to SSH Google Cloud Engine instance through gcloud & Putty from Windows 10

OP has resolved this issue by copying his SSH keys to authorized_keys file. This issue can be caused if Google accounts daemon is not running on your VM. This daemon is responsible for syncing ssh keys and user account information between the metadata and VM. For more information on accounts daemon you can visit this link.

Best Answer

Related Solutions

Linux – SSH public/private authentication failing in Google compute engine instances

Ssh – Unable to SSH Google Cloud Engine instance through gcloud & Putty from Windows 10

Related Topic