Hi, We have setup discourse on AWS private EC2 and we have mapped private IP of EC2 in AWS Route 53(DNS hosting). On running /discourse-setup getting below which means ec2 machine is able to connect with domain mentioned in Route 53 Hostname for your Discourse? [testkb4.dryice-aws.com]: testkb4.dryice-aws.com Checking your domain name . . . Connection to testkb4.dryice-aws.com succeeded. On running ./discourse-doctor getting below: Discourse version at testkb4.dryice-aws.com: NOT FOUND Discourse version at localhost: NOT FOUND When we are providing EC2 public IP in route 53(DNS hosting) everything is working fine. Will discourse set up run only with public IP or elastic IP of EC2 machine. Pl. help us in this. Rgds, Deepak Bisht

The standard install gets a certificate from let’s encrypt. That requires a public ip. If you need the server not to be accessible from the public internet you’ll have to do some unsupported install, perhaps with a certificate that you obtain some other way or behind a reverse proxy that has a certificate. Running without a certificate isn’t really supported.

Discourse not working on private AWS EC2

Product Support Self-hosting

deepak_b May 3, 2023, 5:41am 3

Thanks Jay for your response. Can you suggest any unsupported installation of this.

Topic		Replies	Views
Discourse setup on aws ec2 doesn't work with default IPv4 DNS Self-hosting hosting	13	1714	September 3, 2021
Running public Discourse server w/o Elastic IP assigned Self-hosting	1	602	December 21, 2021
Guide to configure Discourse on Amazon Web services (AWS) EC2 Self-hosting	3	5576	August 5, 2025
30 Min Installation - Public IP Address/ Domain Access with AWS Self-hosting	2	837	July 24, 2019
[Guide] Host Discourse on AWS EC2 Self-hosting	0	4022	December 3, 2020

Discourse not working on private AWS EC2

Related topics