1 Answer
- Newest
- Most votes
- Most comments
0
There could be be a few possible issues:
- Is your instance firewall configured correctly? When SSH'ing from the Lightsail console, Linux instances need TCP port 22 open for SSH to work.
- Is the instance in a running state? It's also possible that your instance is scheduled for retirement, in which case you'll have received an email about this and you'll need to stop then start your instance (note: rebooting/restarting will not work).
- Is your instance attached to a static IP? If not and you're using a dynamic IP with an external SSH tool to connect, is it possible that the dynamic IP of your instance has since changed?
- It's sometimes possible for heavy CPU usage on the instance to prevent SSH connections from happening; please take a look at your instance's CPU metrics to confirm whether this is the case.
answered 2 years ago
Relevant content
- asked 8 months ago
- asked a year ago
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 22 days ago
The OS level firewall is enabled and started after that the ssh access is restricted. I need to get the console of the light sail server. To update the OS level firewall for ssh access.