- Newest
- Most votes
- Most comments
Connect using EC2 Serial Console and check whether the OS firewall and SSH service are running.
It is possible that the SSH service is not running or that the OS firewall is interfering with the connection, so first you need to connect with EC2 Serial Console and check the status.
Hello.
What error did you get when connecting?
Depending on the nature of the error, please try the troubleshooting steps in the document below.
https://repost.aws/knowledge-center/ec2-linux-ssh-troubleshooting
when I try to login into Putty, Network Error: connection time out, just that. As I said, I put my IP and my .ppk file in the session Putty
Thank you for your reply.
If a timeout error occurs, please check whether the required IP address is allowed in the inbound rules of the security group set for EC2.
Also make sure that EC2's public IP address is correct and that the route table for the subnet where EC2 is running has a route to the internet gateway.
I hope you find the following documentation helpful.
https://repost.aws/knowledge-center/ec2-linux-resolve-ssh-connection-errors
If you are using FreeBSD, I think you can connect using EC2 Serial Console.
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/connect-to-serial-console.html
Please connect with EC2 Serial Console and check if there are any problems with SSH or the OS firewall.
that one works so with ec2 Serial console works , but I need to connect at Putty with it and WinSCP
that's giving me after the command ps aux | grep sshd in EC@ --- root 732 0.0 0.4 21068 8120 - Is 10:49 0:00.00 sshd: /usr/sbin/sshd [listener] 0 of 10-100 startups (sshd) root 962 0.0 0.1 12812 2336 u0 S+ 11:24 0:00.00 grep sshd
and after pfctl -s info Status: Disabled Debug: Urgent
State Table Total Rate
current entries 0
searches 0 0.0/s
inserts 0 0.0/s
removals 0 0.0/s
Counters
match 0 0.0/s
bad-offset 0 0.0/s
fragment 0 0.0/s
short 0 0.0/s
normalize 0 0.0/s
memory 0 0.0/s
bad-timestamp 0 0.0/s
congestion 0 0.0/s
ip-option 0 0.0/s
proto-cksum 0 0.0/s
state-mismatch 0 0.0/s
state-insert 0 0.0/s
state-limit 0 0.0/s
src-limit 0 0.0/s
synproxy 0 0.0/s
map-failed 0 0.0/s
root@freebsd:~ #
i found this in putty love event 2023-11-20 15:35:57 Looking up host "18.196.150.185" for SSH connection 2023-11-20 15:35:57 Connecting to 18.196.150.185 port 22 2023-11-20 15:35:57 We claim version: SSH-2.0-PuTTY_Release_0.79 2023-11-20 15:36:18 Failed to connect to 18.196.150.185: Network error: Connection timed out 2023-11-20 15:36:18 Network error: Connection timed out
Relevant content
- asked 7 months ago
- asked 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your reply. If a timeout error occurs, please check whether the required IP address is allowed in the inbound rules of the security group set for EC2. Also make sure that EC2's public IP address is correct and that the route table for the subnet where EC2 is running has a route to the internet gateway. I hope you find the following documentation helpful. https://repost.aws/knowledge-center/ec2-linux-resolve-ssh-connection-errors