Hi discourse community, I am new to discourse and just testing the setup of discourse on an AWS ec2 instance following discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub. However, I wasn’t able to spin it up. Here is problem I am having: Before purchasing all the resources, I wanted to try out the website without a domain name, so I used Public IPv4 DNS of that instance as the hostname of discourse and to access the site, e.g. https://ec2_ip_address.us-west-1.compute.amazonaws.com/. I opened up the port 80, 443 on the instance via the security group, and verified these ports are accessible from public network (tested with python simple server). But I get “This site can’t be reached” in browser after starting the discourse server with ./discourse-setup or ./launcher rebuild app. I tried the discourse doctor, and it returns Discourse version at ec2-ip_address.us-west-1.compute.amazonaws.com: NOT FOUND Discourse version at localhost NOT FOUND I am not 100% sure if email setup is working, but I assume site accessibility is a separate problem with email. Can anyone point me what is missing or how can I debug this issue? thanks a lot!

Welcome to the Meta Discourse Community :slightly_smiling_face: It may be unrelated, but I’m noticing an inconsistency here: [תמונה] ys2843: ec2 _ ip_address.us-west-1.compute.amazonaws.com [תמונה] ys2843: ec2 - ip_address.us-west-1.compute.amazonaws.com

Hi Jonathan, Thanks for checking. I omitted the ip address here, the url should be correct.

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.

[תמונה] ys2843: I opened up the port 80, 443 on the instance via the security group, and verified these ports are accessible from public network (tested with python simple server). Can you verify that your can access the server via the hostname?

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. Agreed. I will pay attention to the build log and see if there is something wrong. How can I debug if there is error in the log? Can you verify that your can access the server via the hostname? Yes, I verified the hostname and the ports are accessible in browser. both 80 and 443. I created a python http server simply serving some files, and I can see response in the browser

Do you see anything in the logs? Something like /var/discourse/shared/standalone/logs/var-log/nginx/error.log There should be an issue with let’s encrypt and aws. Even if it were your own domain, if you rebuilt a bunch of times you could have used to your quota.

[תמונה] pfaffman: There should be an issue with let’s encrypt and aws. Funny you should mention that. :slightly_smiling_face: It’s what initially drew me to this topic. I help a lot of people over at https://community.letsencrypt.org and thought this topic might be in my wheelhouse to assist. To apply any of my tools I would need to know the real domain names.

@ys2843 Can U update what happened later , I am stuck with the exact same issue .

Are you trying to use an aws domain name? Don’t. Use your own. Did you look at the logs? If you did a bunch of rebuilds you’ll also hit let’s encrypt rate limits.

@pfaffman Background : Setting up a minimal discourse forum as a proof of concept on aws, trying to minimize the cost Is there any way to use AWS provided domain name Heuristic example : ec2-ip_address.us-west-1.compute.amazonaws.com I don’t have a domain name purchased , is there any way to avoid this . Warning in setup documentation : Discourse will not work from an IP address, you must own a domain name such as example.com to proceed.

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

תמיכה התקנה

pfaffman (Jay Pfaffman) 13 ביולי,‏ 2021,‏ 12:09am 5

Can you verify that your can access the server via the hostname?

נושא		תגובות	צפיות
Discourse not working on private AWS EC2 Self-hosting	2	707	3 במאי,‏ 2023
How to install Discourse in the AWS EC2 Instances(Ubuntu Server LTS)? Self-hosting	36	5517	30 במרץ,‏ 2019
Discourse instance unreachable on AWS Product Support	27	4374	8 בפברואר,‏ 2017
30 Min Installation - Public IP Address/ Domain Access with AWS Self-hosting	2	839	24 ביולי,‏ 2019
Problem setting up on EC2, due to conection issue Self-hosting	4	841	16 במרץ,‏ 2020

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

נושאים קשורים