- Yes, I checked it.
- 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
I entered the command, here is the 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 in out source destination 16012 108M DOCKER-USER all -- * * 0.0.0.0/0 0.0.0.0/0 16012 108M DOCKER-ISOLATION-STAGE-1 all -- * * 0.0.0.0/0 0.0.0.0/0 7953 107M ACCEPT all -- * docker0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 86 4460 DOCKER all -- * docker0 0.0.0.0/0 0.0.0.0/0 7973 807K ACCEPT all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- docker0 docker0 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 8 packets, 600 bytes) pkts bytes target prot opt in out source destination Chain DOCKER (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:443 15 780 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:80 Chain DOCKER-ISOLATION-STAGE-1 (1 references) pkts bytes target prot opt in out source destination 7973 807K DOCKER-ISOLATION-STAGE-2 all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 16012 108M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (1 references) pkts bytes target prot opt in out source destination 0 0 DROP all -- * docker0 0.0.0.0/0 0.0.0.0/0 7973 807K RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) pkts bytes target prot opt in out source destination 16012 108M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1ddff40f95d2 local_discourse/app "/sbin/boot" 4 minutes ago Up 4 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app
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:
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 / Gitstep, finished
Edit Discourse Configurationand changed AWS EC2 Security Group like this. I enter my FQDN I input in
./discourse-setup, but it displayed:
This site can’t be reached(because of its server IP address could not be found.)
What have you not done?
I just bought a domain on NameSilo, but I don’t change any settings…
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 Amazon.
Your screenshot shows
discourse.example.com - I’m assuming that’s not the domain you’ve trying to work with. It might help if you give us more information about the specific configuration so that we can advise on which records to create.
NameSilo and/or Amazon aren’t psychic, they have no knowledge of one another, it’s up to you to create the necessary DNS entries so that one refers to the other.
Once DNS is correctly configured you will need to wait for the records to propagate, then rebuild your app (./launcher rebuild app) so that Let’s Encrypt can enroll the certificate.
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
so, don’t need to check ports 80 and 443 are not blocked, right?
Thanks, the FQDN is discourse.tircklehub.com. But why I need to rebuild my app again?
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.
I’m using Let’s Encrypt. I rebooted Instance and without rebuild app, but the page loaded successfully. Why did it happened?
Isn’t I need to generate a certificate again when I rebooted Instance?
According to my browser, that domain doesn’t resolve.
Because I stopped the Instance(AWS only provide 750 hours EC2 Instance free tire.). But when I rebooted Instance and without rebuild app again, the page can load successfully.
Now I start the Instance without
./launcher rebuild app. I can visit is successfully. What about you?
So why @Stephen said that?
First question, [at]Stephen told me, I need to:
because of I’m using Let’s Encrypt, and the reason is:
But, I rebooted Instance, configured DNS and without run command
./launcher rebuild app, the welcome page loaded successfully. So the question is how did it happened?
Second questions, how to auto renew Let’s Encrypt certificate?
like this Topic said(I’ve already using
./discourse-setup to enable Let’s Encrypt)?
It will auto renew. You’re all set.
So you mean it will auto renew and generate certificate automatically?