- Más nuevo
- Más votos
- Más comentarios
Hello moongya,
"No route to host" error suggests that there could be some network issue on your instance or that you are not connecting to correct address / host.
For network issue, check if your instance is passing all its system status checks. If some of them are failed, follow this AWS documentation:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html
You can share with me your instance console logs, they are available in AWS EC2 console:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html#instance-console-console-output
As for the second reason, you have mentioned that this has happened after reboot.
Was that reboot or stop and start operation?
If stop and start, your IP address has changed if you have not used Elastic IP. This would explain "No route to host" - you simply do not connect to your instance.
Check your current IP and try to connect to it:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#working-with-ip-addresses
If this was the case, I would recommend using Elastic IP - this is static IP address that does not change upon stop and start operation. It is also free of charge if your instance is running:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
Please note, when you assign Elastic IP to your instance, its IP will change. You cannot convert non-Elastic IP to Elastic one.
I hope that this will help you, if not feel free to reach out to me.
Daniel
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 2 años