CODEWITHSUNDEEP
macosamazon-web-servicesamazon-ec2ssh
Gustavo Mungarro
Gustavo Mungarro

Reputation: 41

Can't SSH into EC2 from my mac but can from other devices

I am trying to connect into an EC2 instance (i am using a mac) which has a Security Group allowing all inbound traffic over ssh (port 22) but i'm unable to access. I'm having a little delay before getting an Operation timed out.

I already tried it over other devices such a raspberry pi and another macbook and the connection was successful. I got access to the raspberry pi over ssh and tried the connection to my EC2 from the terminal; thought my ssh client or the port status could be the issue but after doing this i'm not really sure if this is the case.

This is the message i get when trying to connect:

ssh: connect to host x.x.x.x port 22: Operation timed out

One thing I noticed is that I used a different .pem file which is supposed to not work for that instance and the error was the same, it looks like my Mac cannot reach it.

Things already verified:

Any help is really appreciated it.

-- UPDATE --

This issue rose in my work machine. Got a different laptop due to other issues and problem fixed, looks like it might have been something related to ports or some sort of configuration. Thought it was a problem with AWS but now it's working fine. Sadly I couldn't debug enough to know what the exact issue was. Thanks to everyone who helped out!

Upvotes: 4

Views: 2489

Answers (1)

Binh Nguyen
Binh Nguyen

Reputation: 2157

It seems that you can remote by other devices and this issue is only still happening on your MAC. Try this on your MAC and try to remote again:

Flush your DNS

I don't know which Mac OS you are using so I put the link here: (https://help.dreamhost.com/hc/en-us/articles/214981288-Flushing-your-DNS-cache-in-Mac-OS-X-and-Linux)

If still cannot, you can try to open some protocol ports on that instances like:

ICMP, Echo Reply, ...

then try to reach by that protocol commands:

Ping, telnet, ...

If the result is cannot too, so it must be that your MAC cannot even reach to that instance network, then try to ensure that your MAC can reach the instance's network first.

Upvotes: 1

Related Questions