I’m trying to migrate an instance of Discourse form Digital Ocean over to an AWS EC2. The installation of the new instance seems to work without a hitch, however the EC2 discourse instance seems to be unreachable from my browser. Any idea what this could be causing this and what a fix might be?

[image] auryn_macmillan: I’m running Ubuntu 16.04 I only really work with RHEL distros, but you can try this command to see if there’s a firewall running: sudo ufw status verbose If it’s running, this command will disable it: sudo ufw disable

I’m open to trying a different distro, I’ve been wanting an excuse to play with some others anyway.

sudo ufw status verbose Status: inactive

[image] auryn_macmillan: I’m open to trying a different distro, I’ve been wanting an excuse to play with some others anyway. I’d hate for you to provision a new EC2 and run into the same issue. Can you post a screenshot of your security group rules? If you do rebuild, I recommend CentOS over…

[image] I’ll try a rebuild on CentOS later tonight and will let you guys know how I go.

Alright, so I just went through the install process on a fresh CentOS 7 EC2. Everything seems to have gone smoothly, although I do notice a something weird: $ ./launcher start app which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin) 6dd44a3a02af Nothing to do, your container has already started! …

[image] auryn_macmillan: which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin) I get this error, too. It’s not a problem because the launcher locates the Docker binary elsewhere. [image] auryn_macmillan: Anyway, this instance seems to be suffering the same problem. So I’m guessing this …

Incoming rules: [image] Outgoing rules: [image] Confirmation that the EC2 is using this security group: [image]

Bizarre. And you can still SSH in, but not connect on any port besides 22? If you want, you can PM me the credentials for a temporary account and I can log in to have a quick look around. I don’t mind if you can do it before I leave for a New Year’s party. :slight_smile: Otherwise, you can open a t…

Yeah it’s really bizarre. Will DM you.

Discourse instance unreachable on AWS

Product Support

CaptainChemist (Stephen Jensen) February 6, 2017, 6:26pm 24

Ha, I got it! Your tip about let’s encrypt was correct. Once I reran the set up after namecheap had a chance to point from my domain to my IP address, everything worked perfectly.

Thanks again!

Topic		Replies	Views
How to install Discourse in the AWS EC2 Instances(Ubuntu Server LTS)? Self-hosting	36	5375	March 30, 2019
Discourse setup on aws ec2 doesn't work with default IPv4 DNS Self-hosting hosting	13	1664	September 3, 2021
Problem setting up on EC2, due to conection issue Self-hosting	4	830	March 16, 2020
Configure Discourse - Environment AWS Linux 2 AMI and Apache2 (httpd) Self-hosting advanced-setup	3	2457	July 7, 2023
After Discourse installation can’t reach it in browser Self-hosting	24	4318	September 5, 2020

Discourse instance unreachable on AWS

Related topics