EC2实例“花了太长时间无法响应" [英] EC2 instance 'took too long to respond'

查看:296
本文介绍了EC2实例“花了太长时间无法响应"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个基于NodeJS构建的网站,目前我正尝试将其部署在AWS的免费层上.

I have a site built on NodeJS, which I am currently trying to deploy on the free tier on AWS.

到目前为止,我已经创建了一个实例,启动了它,我可以通过SSH(控制台)连接到我的实例,并且已经成功地从Git存储库中提取了我的文件.但是,当我尝试浏览公共DNS时,我得到: ec2-54-252-151-208.ap-southeast-2.compute.amazonaws.com:8080 花费了很长时间才能响应.

So far I have created an instance, launched it, I can connect via SSH (console) to my instance, and have successfully pulled my files from my Git repository. However, when I try to browse my public DNS, I get: ec2-54-252-151-208.ap-southeast-2.compute.amazonaws.com:8080 took too long to respond.

我还查看了安全组上的设置(如另一篇文章所建议),并确保允许入站和出站"HTTP"和"HTTPS"流量(以下屏幕截图):

I have also had a look at the settings on security group (as recommended on a different post) and ensured that inbound and outbound 'HTTP' and 'HTTPS' traffic are allowed (screenshot below):

入站设置:

出站设置:

关于导致此问题的其他原因的任何想法?非常感谢您的帮助.谢谢.

Any ideas on what else could be causing this issue? I would greatly appreciate your help. Thanks.

推荐答案

似乎您需要将8080端口添加到入站IP规则中.

It looks like you need to add port 8080 to your inbound IP rules.

这篇关于EC2实例“花了太长时间无法响应"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆