I’m editing a guide of install Discourse in the AWS EC2 Instances(Ubuntu Server LTS) in Chinese Simplified. I’m also a newbie of Rails, Linux shell and Web Development. This is the part I have already edited. Is there are any errors? Thanks.

Yes, I checked it. [EC2 Security Groups] Yes. Asia Pacific (Seoul).

Next level down the stack that could be stopping it would be a firewall. Does iptables -nvL output anything? Past that is the discourse container actually running? Does it appear in a docker ps?

I entered the command, here is the output: [Bild] schleifer: iptables -nvL output Chain INPUT (policy ACCEPT 9 packets, 648 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt …

I tried to visit Instances’s IPv4 Public IP, and it displayed that: [chrome-error___chromewebdata_(Laptop%20with%20HiDPI%20screen)%20(1)]

You need to use the name you’ve configured in DNS to access your instance, not the IP. Accessing discourse via IP address isn’t supported.

@Stephen Umm, I tried to visit the FQDN I input in ./discourse-setup , but: [Bild] Lee533: Page displayed This site can’t be reached [chrome-error___chromewebdata_(Laptop with HiDPI screen).png]

What have you done? I have bought a domain on NameSilo, registered a AWS account, and launch a Instance, connected to the Instance from Windows using PuTTY , follow Set up Discourse in the cloud in under 30 minutes from Install Docker / Git step, finished Edit Discourse Configuration and changed A…

So you’ve not done anything to tell NameSilo about your EC2 server at Amazon? The way DNS works is that you tell the DNS server about the resources you’re trying to publish under that domain name. You need to configure an ‘a’ record at NameSilo for your Discourse instance, linked to the IP at Amazo…

[Bild] Lee533: What have you not done? I just bought a domain on NameSilo, but I don’t change any settings… You need to go to NameSilo and create an A record that connects your FQDN to your site. You might also need to make sure that ports 80 and 443 are not blocked.

Thanks, I have [Bild] Lee533: changed AWS EC2 Security Group like this so, don’t need to check ports 80 and 443 are not blocked, right?

Discourse auf AWS EC2-Instanzen (Ubuntu Server LTS) installieren

Unterstützung Installation

Stephen (Stephen) 28. März 2019 um 02:04 35

If you’re using Let’s Encrypt then once DNS is configured it needs to generate a certificate, which is done when the container is built.

Thema		Antworten	Aufrufe
Discourse instance unreachable on AWS Support	29	4023	30. April 2019
Discourse setup on aws ec2 doesn't work with default IPv4 DNS Self-hosting hosting	13	1480	3. September 2021
Configure Discourse - Environment AWS Linux 2 AMI and Apache2 (httpd) Self-hosting advanced-setup	3	2284	7. Juli 2023
After Discourse installation can’t reach it in browser Self-hosting	24	4048	5. September 2020
Problem setting up on EC2, due to conection issue Self-hosting	4	766	16. März 2020

Discourse auf AWS EC2-Instanzen (Ubuntu Server LTS) installieren

Verwandte Themen