not able to connect SSH through VM instance in google cloud iam getting connection failed error
need help
Related
I have a SSH service connection in Azure DevOps using username and password. It was working till last/before week. Azure DevOps cant connect to VM any more, there has been no changes. I can still connect to VM using Putty of ssh.
pipeline task instantly fails with below error:
Failed to connect to remote machine. Verify the SSH service connection details. Error: Error: Handshake failed: no matching key exchange algorithm.
I created an Azure Container Registre some days ago, and now it's impossible to login to this registry with docker login command. I always get this error message:
Error response from daemon: Get https://XXXXXXXXX.azurecr.io/v2/: dial tcp: lookup XXXXXXXXX.azurecr.io on [::1]:53: read udp [::1]:52627->[::1]:53: read: connection refused
Docker client may throw such error when it is unable to connect to the local Docker daemon properly. So, Restart/Reinstall-Docker should mostly fix that.
I'm trying to evaluate spinnaker on AWS.
I followed the document to setup VPC in AWS. I'm able to run Spinnaker at http://localhost:9000, but when I click on the new application in the Spinnaker UI, I see this error on the terminal.
channel 7: open failed: connect failed: Connection refused.
I'm unable to create a new application.
It is possible that port 8084 is blocked. The Spinnaker UI(Deck) needs to be able to communicate with the API(Gate) over port 8084.
In AWS, try opening port 8084, same way you did for port 9000.
Port is up, firewall disabled, but connection is rejected with message:
"Read from socket failed: Connection reset by peer".
Other services in the same host are responding well.
SSH through Google Cloud Console gets the same error.
Is there any other method for Google Compute Engine to get shell?
Yes, there is a way to get shell, and it is through the serial port, a really useful feature Google Cloud provides.
There, I saw the error was about key file permissions:
Sep 30 10:51:02 localhost sshd: Permissions 0775 for '/etc/ssh/ssh_host_rsa_key' are too open.
And by assigning 0600 perms to this file everything went back to normal.
I had created the the keys for the google cloud instance and when I try to ssh into the instance. I'm unable to access it and getting an error: port 22: Operation timed out. This happens through both the desktop ssh client and also through the google cloud shell. I had created a project wide keys in the metadata section to access it.
Any insights on why I'm unable to connect will be highly helpful. The instance was created a day ago.
Couldn't figure out why I was not able to ssh into the server previously. But now there is a single click option to ssh into the google cloud instances. You may close this thread.