Ssh program unexpectedly exited

But if I am missing something, please so indicate and suggest the fix for this error. Basically I can't get any efficient work done at this point having to ssh in so many times. Then, you must update the ssh keys in your metadata by. If the default network was edited, or if not using the default network, you may need to explicitly enable ssh access by adding a firewall-rule :. Sometime after creating the instance using the gcloud sdk ssh snippet provided via GCP console stopped working and continually errors with making connecting to ssh on the instance only available through browser via GCP console for the compute instance in question.

Not to mention this has happened to me on many different instances some without touching the default account permissions after initial setup and deployment which is overly frustrating. Cause for no reason it just stops working The only thing that worked for me was creating a new user to connect with through gcloud sdk! I've tried updating the account, tried deleting the user and credentials from the instance, nothing appears to work. Just doesn't work But creating a new user works every time, and once the user is created you can keep using that user via gcloud sdk.

It's a work around, and I hate work around's for things like this but for my sanity this works at least until I can figure out how to reset the default account permissions, so if anyone has any ideas there or can point me in a direction for that I'd more than appreciate it!

IT was my mistake stating that the default firewall would allow all connections into an instance. The contrary turned out to be true. Please refer to an appropriate firewall rule must be set up to allow connection into an instance.

If you have Identity-Aware Proxy IAP enabled for your setup, try adding the --tunnel-through-iap option to the gcloud compute ssh command. More information for people landing on this page, if you're using preemptible instances to save some compute costs, that could also be the reason for getting kicked out like this. Your instance may have just randomly stopped. In my case, the I had created a bootable disk for the VM without adding the information of what source-image it needs to have.

Because of this, even though the instance was coming up alright and ssh-allow rule was there, the VM was not booting up.

I had the problem where after clicking on the SSH button it would keep trying to establish a connection and fail. After long struggle I resolved it by adding Service Account User role to myself. If your account was created after the VM instance was created, it might result in this situation. I know this was opened a long time ago, but for a more recent update on this topic.

I had the same trouble connecting via ssh. It was giving the error code Obviously there was a connectivity issue. However, to fix this problem I had to go to the specific network and create a rule under the network Firewall Rules.

I eventually had to delete my instance and make a new one with the same disk. For me, my other teammates were able to login into the machine, but not me. So I asked them to create a user of my name with sudo rights, logged into serial console and changed passwordAuthentication to yes followed by sudo service ssh restart for few this could be sudo service sshd restart.

Reinitializing the gcloud with "gcloud init" and generating new ssh keys resolved the problem for me. I had connected the serial control and had checked logs.

Then I had resized disk as written in this document. What worked for me: I tried reinstalling lots of things and re-initializing various config and then landed on a thread which suggest to change the Internet network you are using and it worked!! It's possible you have a rule that only allows whiltelisted IPs to ssh into a gcloud VM. I got the same error and tried gcloud config ssh as mentioned previously to no avail. I then checked that the IDs and roles of serviceaccount and developer had 'editor' permissions, and that was fine.

I started a new instance and logged out of all of my other google accounts and it still threw the error. Then, I restarted my computer and did not log back into my other google accounts.

That fixed it. Reason being:. If this is the case with you, then fix is simple: remove the instance metadata entry for that user, key combo have attached an image for ref, just click X and remove your faulty key and try ssh again.

If you have Identity-Aware Proxy IAP enabled for your setup, try adding the --tunnel-through-iap option to the gcloud compute ssh command. More information for people landing on this page, if you're using preemptible instances to save some compute costs, that could also be the reason for getting kicked out like this. Your instance may have just randomly stopped.

In my case, the I had created a bootable disk for the VM without adding the information of what source-image it needs to have. Because of this, even though the instance was coming up alright and ssh-allow rule was there, the VM was not booting up.

I had the problem where after clicking on the SSH button it would keep trying to establish a connection and fail. After long struggle I resolved it by adding Service Account User role to myself. If your account was created after the VM instance was created, it might result in this situation. I know this was opened a long time ago, but for a more recent update on this topic.

I had the same trouble connecting via ssh. It was giving the error code Obviously there was a connectivity issue. However, to fix this problem I had to go to the specific network and create a rule under the network Firewall Rules.

I eventually had to delete my instance and make a new one with the same disk. For me, my other teammates were able to login into the machine, but not me. So I asked them to create a user of my name with sudo rights, logged into serial console and changed passwordAuthentication to yes followed by sudo service ssh restart for few this could be sudo service sshd restart. Reinitializing the gcloud with "gcloud init" and generating new ssh keys resolved the problem for me. I had connected the serial control and had checked logs.

Then I had resized disk as written in this document. What worked for me: I tried reinstalling lots of things and re-initializing various config and then landed on a thread which suggest to change the Internet network you are using and it worked!! It's possible you have a rule that only allows whiltelisted IPs to ssh into a gcloud VM.

I got the same error and tried gcloud config ssh as mentioned previously to no avail. I then checked that the IDs and roles of serviceaccount and developer had 'editor' permissions, and that was fine.

I started a new instance and logged out of all of my other google accounts and it still threw the error. Then, I restarted my computer and did not log back into my other google accounts. That fixed it. Reason being:. If this is the case with you, then fix is simple: remove the instance metadata entry for that user, key combo have attached an image for ref, just click X and remove your faulty key and try ssh again.

In this case the best way to fix it is to go to your home directory in your computer check the hidden files and find the folder ". Just delete this folder and re-open your bash terminal. Then run again your gcloud vm command. Type "Y" and gcloud will setup the new protocols by creating a brand new updated. After that you should be able to access your VM with your gcloud command without any problem.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. ERROR: gcloud. Asked 7 years, 3 months ago. Active 14 days ago.

Viewed 74k times. Thanks in advance. Last edited by doktor on Mon Oct 26, pm, edited 2 times in total. Do you have a second box in your network which is named "linux"? Linux , mageia 5 as described previously 2. Windows 7 laptop 3. I could connect and see the self linux files on the linux network icon few day ago, but suddenly it stopped and I get the error message.

Does this info help in any way? Tks JJF.