Forever connecting to custom gce vm

[tczank]

Dear all,

I've been getting a problem since last week. I can no longer successfully connect to a custom gce vm instance. I've checked with my company DE team to see if my user had the appropriate permissions, and it does. Other members of my team can successfully connect, but I can't. This started happening after I tried to install a package through pip from my github repository on a colab session that was connected to the custom gce vm. I've tried cleaning the cookies from my browser, using a different pc and a different browser. I always get stuck forever connecting to that custom gce vm. I can use colab with the default runtime settings.

Cheers,

Thomas

[DarwinVinoth]

Did you try a web-based SSH session? 

Or through the gcloud utility? 

gcloud compute ssh your-vm-instance-name --zone=your-vm-zone --dry-run


Thanks, 
Darwin Vinoth.
Linkedin 

[reinc]

Hi @tczank,

Welcome to Google Cloud Community! 

The most probable cause is that the pip install command, run while you were using Colab connected to your Google Compute Engine (GCE) VM, messed with the SSH configuration. Specifically, it might have changed permissions or contents of your ~/.ssh/authorized_keys (which controls who can log in) or /etc/ssh/sshd_config (which configures the SSH server itself). This could have happened because the installed package had a faulty setup script or because something unexpected happened when Colab's environment interacted with your SSH settings.

It is recommended to pip reinstalls to update all the packages to the latest compatible versions, you may check the documentation.

If the issue still persists and needs further assistance with specific configurations, please reach out to our Google Cloud Support team.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[tczank · Accepted solution]

Thanks for the support. The DE team could solve the problem with:

gcloud compute ssh vm-1 --zone=asia-northeast1-b
(SSH into the VM)
docker rm k_default && sudo systemctl restart k_default

from

https://github.com/googlecolab/colabtools/issues/2880#issuecomment-1327380070