- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
The best place to raise this question is with our support team because they can troubleshoot with you.
However, some other steps:
- Have you tried restarting the instance from the console?
- Has anything else changed (Security Groups, NACLs).
- Can you reach other instances using SSH?
Given that EC2 Instance Connect isn't working my guess is that something is "wrong" in the operating system and a reboot might resolve it.
More of a suggestion for future usage, take a look at the Systems Manager session manager, in case you're not able to SSH it will help with access easier than EC2 instance connect in my experience: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html
What @Brettski@AWS mentioned is also what I'd recommend for troubleshooting it could be that the system is just in a hung state and a reboot from the console will resolve the connection issues. You can take a look at the CloudWatch metrics as well to see if perhaps you hit high CPU and that's why the machines has issues.
@Rob_H Thanks for reply. As @Brettski@AWS mentioned, restart instance will recover to normal state. I think system is freeze and can't restore to normal state. As you suggested, i will try Systems Manager session manager later.
I have the same problem but no joy with reboot :'( I think it's an authorization problem because I faced the awful "sudo must be owned by uid 0" error message after trying to update my servers SSL's and then reinstated mistakenly typing "chown root:root /etc" (instead of /etc/sslSubfolder...)... So now I can't access this instance (and this instance only) neither over SSH nor over the web based EC2IC. Serial connection is not possible due to incompatible instance type. The consequence is that I can't fix the authorization cmd mistake I made since every troubleshouting doc I see involves connecting over SSH... I can't even restart the SSH service on this instance. Restarting the instance didn't change anything. Even hard restart which may also have caused more issues although using elastic ip's so records are intact but apache config seems altered too.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
thanks for reply. 1.restarting instance haven't try yet. i will try that. 2.Security group, NACL haven't changed since created. 3.other instances can connect without problem.
@Brettski@AWS As you suggested, instance reboot return to get normal state. Thanks again.