# Discourse instance unreachable on AWS

**URL:** <https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006>\
**Category:** Product Support\
**Created:** [December 31, 2016, 4:40pm UTC](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006 "2016-12-31T16:40:30Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DanielMarquard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danielmarquard/32/74010_2.png) [@DanielMarquard](https://meta.discourse.org/u/DanielMarquard)\
**Post date:** [December 31, 2016, 9:20pm UTC](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006/8 "2016-12-31T21:20:28Z")

</div>

> [@auryn\_macmillan](#):
>
> I mean if I try to browse to the instance using the IP address, the connection is refused.

> [@auryn\_macmillan](#):
>
> Yes, I can SSH in without issue.

It seems like it could be an issue with the instance itself. If you haven’t done so already, verify that Nginx is running on your EC2 (or in the container) and that the port is accepting traffic.

```sh
ps aux | grep -i nginx
telnet localhost 443

```

Are you running Amazon Linux? I use CentOS on AWS, but you can try these commands to disable the firewall, if one is running:

```sh
systemctl stop firewalld
systemctl stop iptables
systemctl stop ip6tables

```

Although less likely, the traffic might somehow be blocked on the VPC, so make sure your [VPC network ACLs](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html) look good.

---

_[View the full topic](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006)._