# הגדרת Discourse ב-aws ec2 לא עובדת עם ברירת מחדל IPv4 DNS

**URL:** <https://meta.discourse.org/t/discourse-setup-on-aws-ec2-doesnt-work-with-default-ipv4-dns/196789>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [11 ביולי,‏ 2021,‏ 7:10pm UTC](https://meta.discourse.org/t/discourse-setup-on-aws-ec2-doesnt-work-with-default-ipv4-dns/196789 "2021-07-11T19:10:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)\
**Post date:** [12 ביולי,‏ 2021,‏ 6:11am UTC](https://meta.discourse.org/t/discourse-setup-on-aws-ec2-doesnt-work-with-default-ipv4-dns/196789/4 "2021-07-12T06:11:18Z")

</div>

The `Not found` status on your hostname is most probably due to the site not being live. You’ll have to share more from your discourse-doctor log.

Does the rebuild/bootstrap complete successfully?

If the EC2 instance is underpowered then there is a chance that discourse would take some time (~3-5 mins in some cases)

What you should be looking at is if your build completes successfully then with `docker ps` verify that the container is running and listening on 80 & 443. Once that’s verified, the problem is with the AWS security group and not the install itself.

---

_[View the full topic](https://meta.discourse.org/t/discourse-setup-on-aws-ec2-doesnt-work-with-default-ipv4-dns/196789)._