| Can't FTP, SSH or Ping my instance Posted on: Oct 31, 2015 3:52 PM | | This question is not answered. Answer it to earn points. |
I've had no problems with my instance in the past, and all of a sudden I can't FTP, SSH or ping my instance.
The Public IP is : 50.18.176.3
I set up an ICMP rule in my security group -- which doesn't make sense why I'd have to do this because I've never had a problem before -- and it didn't change anything.
Thanks |
|
| Replies: 2 | Pages: 1 - Last Post: Nov 6, 2015 12:02 PM by: arkeon |
|
|---|
|
| Re: Can't FTP, SSH or Ping my instance Posted on: Nov 5, 2015 2:58 PM | Hello,
Thank you for the post.
I took a look at your instance with IP address: 50.18.176.3 and found that it is operating normally at the infrastructure level. I also tried to connect on port 22 (SSH) and I was able to connect using a 'netcat' command. Please find the output of my command below:
nc -v 50.18.176.3 22
Connection to 50.18.176.3 22 port tcp/ssh succeeded!
From the above output, it seems that the instance is allowing connections on port 22 (SSH).
In general, please refer to this documentation for more information about 'Troubleshooting Connecting to Your Instance': http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
Also, I tried to perform ping and I was unable to ping the instance on IP: 50.18.176.3. Looking at the instance's security group: default, I found that you have specified the same security group: default, as a source to allow ICMP traffic. This rule allows instances associated with this specified security group (default) to ping instances associated with this security group.
In general, when you specify a security group as the source or destination for a rule, the rule affects all instances associated with the security group. Incoming traffic is allowed based on the private IP addresses of the instances that are associated with the source security group.
You can find more information about 'Security Group Rules' on this documentation: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#security-group-rules
I hope the above information helps.
Thank you,
Nikhil |
|
|
| Re: Can't FTP, SSH or Ping my instance Posted on: Nov 6, 2015 12:02 PM | Thank you for your response!
The ICMP rule I had just added recently because I read that would help. I couldn't ping the instance before I added the rule. I removed it and still can't ping it.
I'm unable to SSH or FTP into my instance unless I reboot the instance, and after somewhere around 4 hours after rebooting I can no longer SSH or FTP.
The SSH error I get is either:
Read from socket failed: Connection reset by peer
OR
ssh_exchange_identification: read: Connection reset by peer
And my FTP says that it's not accessible.
I simply can't get an answer on this. AWS said to upgrade my instance size. This can't be it as I have low traffic.
Is the instance corrupted?
It it getting spammed? |
|
|
| | Answered question | | Unanswered question with answer points still available | | Unanswered question |
| Ace: 2000+ pts | | Expert: 750-1999 pts | | Guide: 300-749 pts | | Enthusiast: 50-299 pts | | Newbie: 5-49 pts | | Amazonian |
|
I was able to ssh to a Ubuntu 16.04.2 server before reboot. So after reboot I tried to ssh, but failed with message sshexchangeidentification: read: Connection reset by peer. Weird part is that, after wait for 10 minutes or so, I am able to ssh to the server. Is there a time lock? If so how to reset that? Lovetokenui-MacBook-Pro:02AWS lovetoken$ ssh -i 'AWSkeyonSeoul.pem' ubuntu@52.79.94.58 sshexchangeidentification: read: Connection reset by peer 이처럼 'sshexchangeidentification: read: Connection reset by peer' 이라는 메시지 이후 리눅스 우분투에 접속이 안되고 터미널로 빠져나옵니다. 'Connection reset by peer' means the TCP stream was abnormally closed from the other end. I think the most likely explanations are that the remote server process handling the connection has crashed, or else some network device (like a stateful firewall or load balancer). From PuTTY I just get 'Network error: Software caused connection abort'. From OpenSSH3.9p1, OpenSSL 0.9.7a Feb 19 2003 I get a 'sshexchangeidentification: read: Connection reset by peer' and back to bash prompt. Both these clients worked fine on this FW before the power-down and move and still work on all other ASAs and PIXs.
Couldn't Read Packet Connection Reset By Peer
Ssh_exchange_identification Read Connection Reset By Peer Aws Login
