1 Answer
- Newest
- Most votes
- Most comments
0
My personal recipe to understand the exact situation is to connect to tcp port 22 (ssh) via your usual telnet client to see if session gets established properly at tcp level. If yes, you know that you have a real ssh issue (public/private key, password). If no, you have an improper network (routing) or security (sec groups) configuration.
So, do you get a tcp session established via telnet on ssh port?
Relevant content
- asked 3 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago
Please provide substantially more details to get an adequate answer. Have you checked all the firewalls involved: Network ACL, Security Group, operating system?
Have checked all the firewalls involved: Network ACL, Security Group, and operating system.
the network error persists.
https://stackoverflow.com/questions/42664340/ubuntu-aws-instance-reachability-check-failed
In this post, it says that Ubuntu 18.04 break the network connectivity and has DHCP problems
Cant connect to SSH and FTP too
Are you running the ssh command from an enterprise laptop or network? It is mostly the case that these ports are blocked by default.