# Forum doesn't load after installing on AWS Linux

**URL:** <https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715>\
**Category:** Support\
**Created:** [March 11, 2022, 8:57am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715 "2022-03-11T08:57:42Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 8:57am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/1 "2022-03-11T08:57:42Z")

</div>

Resolved issue by installing Ubuntu on AWS

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [March 11, 2022, 11:33am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/2 "2022-03-11T11:33:58Z")

</div>

I would first delete the AAAA record. Discourse-setup tests the dns record when it runs, did you install using Discourse-setup?

One guess is that one of your DNS records is wrong.

---

<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:** [March 11, 2022, 11:36am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/3 "2022-03-11T11:36:07Z")

</div>

Do you have a firewall blocking your ports? I can’t even ping the IP address provided so it is hard to guess if the problem lies at the firewall or the droplet itself.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:26pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/4 "2022-03-11T13:26:33Z")

</div>

Alright I’ve deleted it, same outcome.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:27pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/5 "2022-03-11T13:27:57Z")

</div>

No, Discord Setup would not proceed due to port 443 being not assessable (port 80 succeeded though), not due to propagation either, I’ve already waited 24 hours.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:28pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/6 "2022-03-11T13:28:35Z")

</div>

No, no firewalls are present. I double checked with my hosting provider Hostinger, whom said no firewalls for my subdomain/domain were present on their end.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:33pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/7 "2022-03-11T13:33:05Z")

</div>

❗ I’ll post the Discord Doctor log file tomorrow, since Discourse keeps wanting me to rebuild the package each time I reconnect to the SSH instance. (11:32pm AEST for me right now) It takes a good 15 minutes to do.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:38pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/8 "2022-03-11T13:38:26Z")

</div>

Let’s encrypt **PASSED successfully** by the way

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 1:41pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/9 "2022-03-11T13:41:12Z")

</div>

I don’t think its the DNS.. I have a feeling it might be the AWS IP, since when you go to the Public IP it shows the timed out or access refused error as well, where our DNS for the subdomain is pointed to.

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [March 11, 2022, 1:53pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/10 "2022-03-11T13:53:02Z")

</div>

> [@AusAvia](#):
>
> No, Discord Setup would not proceed due to port 443 being not assessable (port 80 succeeded though),

Then something is blocking or using port 443. This is your problem, just like `discourse-setup` told you before you built your first container.

---

<div class="post-metadata">

**Author:** ![Alexander](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander/32/497634_2.png) [@Alexander](https://meta.discourse.org/u/Alexander)\
**Post date:** [March 11, 2022, 1:57pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/11 "2022-03-11T13:57:41Z")

</div>

I have some doubts,

With AWS Linux, do you mean the Amazon Linux 2 image? Or do you use another operating system?

Have you opened the corresponding ports from the AWS Control Panel?

Are you using an Elastic IP?

🤔

---

<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:** [March 11, 2022, 2:20pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/12 "2022-03-11T14:20:52Z")

</div>

I’m not following!  
Are you hosting with Hostinger? or with AWS?

if it is aws, I’m a 100% sure its their firewall (security groups) that is causing all this trouble.

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 2:32pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/13 "2022-03-11T14:32:09Z")

</div>

Amazon Linux 2 operating system

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 2:33pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/14 "2022-03-11T14:33:00Z")

</div>

Our subdomain is provided by hostinger  
The rest is AWS

---

<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:** [March 11, 2022, 2:33pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/15 "2022-03-11T14:33:53Z")

</div>

So you need to get into your aws account, then check the Security Group for the instance to enable Inbound Port 80, 443 for all IPs (0.0.0.0/0)

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 2:34pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/16 "2022-03-11T14:34:15Z")

</div>

![Screenshot 2022-03-12 085741](https://global.discourse-cdn.com/meta/original/3X/c/7/c70b11cfe667a5f2b9a30ced00afe1c6ecb86ecd.png)

---

<div class="post-metadata">

**Author:** ![AusAvia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ausavia/32/252792_2.png) [@AusAvia](https://meta.discourse.org/u/AusAvia)\
**Post date:** [March 11, 2022, 10:54pm UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/17 "2022-03-11T22:54:55Z")

</div>

![34c8832f51806eeec4dadb2e3b51b40f](https://global.discourse-cdn.com/meta/original/3X/3/c/3cc5a0e5a87a248b51618390fada0e8b973d49ae.png)  
This is what it looks like right now is that right, do I need to modify or delete any?

---

<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:** [March 12, 2022, 5:08am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/18 "2022-03-12T05:08:17Z")

</div>

One of these would be linked to your ec2 instance. Find that one first.

Easiest way is to find on the instances tab

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [April 11, 2022, 5:09am UTC](https://meta.discourse.org/t/forum-doesnt-load-after-installing-on-aws-linux/220715/19 "2022-04-11T05:09:11Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
