The network ACLs must allow inbound and outbound traffic from your local IP address on the proper port. Check the network access control list (ACL) for the subnet.There is an internet gateway attached to my VPC (same VPC as my other instances) You need a route that sends all traffic destined outside the VPC to the internet gateway for the VPC. As mentionned above, the security group attached has the port 22 inbound allowed You need a security group rule that allows inbound traffic from your public IPv4 address on the proper port. I followed the troubleshooting steps located at the link below: Įrror connecting to your instance: Connection timed out Other working 3 instances Public IP starts with: 99.79. I have 4 instances in the same availability zone but the problematic one has a different IP range (it was different before as well) Problematic Public IP starts with: 35.182. I also added my IP to the group just in case and it still did not work.That same security group is used on another instance that works fine. I checked the security groups (in case it changed somehow) and the port 22 is allowed inbound.I then stopped/started the instance, got a new IP, changed the info in route 53, the site is back up and running but SSH with the above steps still does not work.SSH from another EC2 instance using the private IP.SSH from another EC2 instance using the public host.This was working before, the connection did not change SSH from PAC (linux SSH client) using the key pair: Getting a time out.Server is still up and running, HTTPS works fine and i can reach the services through the browser but can't SSH. I was able to connect to SSH previously but all of a sudden it stopped working. I've been getting a connection timed out since some days in 1 of our EC2 instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |