- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
In addition, you can:
1/ Check the Security Group whehter the inbound rules is correct or not.
2/ Check the Monitoring and see whether it's out of resouces (eg. CPU).
Did you try to check the logs? Got a screenshot of the instance? EC2 serial console? In last case, rebooted? Can be many things, need to troubleshoot.
Screen shot of the instance shows its on. serial console connect, but we have pem file and we connect via ssh using the pem file that has always worked
Im wondering if the EC2 is non responsive will it advisable to detach this volume from it and attach it to a new instance we spin up? We would then just reconfigure all the site urls on the new server
Did you try rebooting the instance?
Did you take a look at AWS Systems Manager / Node Management / Session Manager? Check if you have any Sessions there you can Terminate and start a new one. And take a look at your Preferences for your sessions that might be blocking you to access your EC2 instance.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
We confirmed that all the inbound rules are correct, and the monitoring did not show any resources running out
I am having same issue.