其他分享
首页 > 其他分享> > [SSH] SSH Troubleshooting

[SSH] SSH Troubleshooting

作者:互联网

1) There's a connection timeout

This is a security group issue. Any timeout (not just for SSH) is related to security groups or a firewall. Ensure your security group looks like this and correctly assigned to your EC2 instance.

2) There's still a connection timeout issue

If your security group is properly configured as above, and you still have connection timeout issues, then that means a corporate firewall or a personal firewall is blocking the connection. Please use EC2 Instance Connect as described in the next lecture.

 

3) SSH does not work on Windows

 

4) There's a connection refused

This means the instance is reachable, but no SSH utility is running on the instance

 

5)  Permission denied (publickey,gssapi-keyex,gssapi-with-mic)

This means either two things:

 

6) Nothing is working - "aaaahhhhhh"

Don't panic. Use EC2 Instance Connect from the next lecture. Make sure you started an Amazon Linux 2 and you will be able to follow along with the tutorial :)

 

7) I was able to connect yesterday, but today I can't

This is probably because you have stopped your EC2 instance and then started it again today. When you do so, the public IP of your EC2 instance will change. Therefore, in your command, or Putty configuration, please make sure to edit and save the new public IP.

 

标签:sure,instance,Troubleshooting,SSH,security,your,EC2
来源: https://www.cnblogs.com/Answer1215/p/14999582.html