Cannot SSH to Lightsail instance via AWS Console. Port 22 is open.

yes I got the same problem too , did u fixed the problem? or the problem still there?

Hello

If you are not able to ssh from the SSH Client you can try from the browser,.

I am only using the browser within Lightsail.

In fact, the problem is account wide. None of my other instances let me connect, and I even tried to create a brand new instance with no data, and even after creating that I couldn't connect.

I think this is an actual Lightsail issue. I've tried different new instances in different regions with different OS or control panels, and I cannot SSH to any of them using the Lightssail connect interface. How do I get Lightsail/Amazon to look at it?

I also have the same problem.

I cannot connect my instance too. SSH client within Lightsail. There is no response with "Connecting to your instance".

In my case, I was able to connect by deleting Cookies (Chrome).
I don't know the cause, but when I couldn't connect, I was getting the following Websocket error in the console log.

WebSocket connection to 'wss://connect-ap-northeast-1.lightsail.aws.amazon.com/ls/websocket-tunnel?~~~~~~~' failed: 
connect @ bundle_vendors.e57657528586c6d4cd3d.js:2

Does anybody know where the answer can be found? As a newbie I'm confused. Please help.

Please open your lightsail console with browser traceless mode.

Same here. I connected to Lightsail and for about 5 or 6 hours later I cannot access it. I use terminal.
I have to stop the instance and start it again. However, this will change the ip address and this is not a solution.

Finally Figured out the issue, by creating another instance & was trying to replicate my issue that is: "ssh: connect to host x.x.x.x port 22: Operation timed out". on my lightsail instance.

Why I am unable to connect to the instance via SSH is that I did turn on the UFW in my ubuntu instance by typing sudo ufw enable, that is the main mistake I made, after doing this when I tried to connect my instance again via same steps, I was unable to connect.

The solution is, whenever we turn on the ufw, we must allow ufw with port 22, by running the command sudo ufw allow 22