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?

Have you set your security group to allow inbound https? So far as I can tell, HTTPS is enabled. I think the user interface could be a bit less fragmented than it seems to be Yeah I’ve often been pretty overwhelmed by the menus/options.

Not that I’m a fully qualified propellorhead, but… [Bild]

[Bild] auryn_macmillan: the EC2 discourse instance seems to be unreachable from my browser. Do you mean that you cannot view the EC2 instance? Can you SSH in? Is your instance behind an Elastic Load Balancer? Verify your security group rules on the EC2 instance, then try telnet <ip> 443 from …

I can help if you provide more info. AWS is my bread and butter. :slight_smile: That would be very much appreciated. Do you mean that you cannot view the EC2 instance? I mean if I try to browse to the instance using the IP address, the connection is refused. Can you SSH in? Yes, I can SSH…

Do you mean telnet to the standard port? That won’t get through with the rules as I have them. You should be able to telnet to port 80 (for http) and port 443 (for https) (and you need a rule for outbound too, I used all traffic 0.0.0.0/0)

[Bild] auryn_macmillan: I mean if I try to browse to the instance using the IP address, the connection is refused. [Bild] auryn_macmillan: Yes, I can SSH in without issue. It seems like it could be an issue with the instance itself. If you haven’t done so already, verify that Nginx is …

It seems like it could be an issue with the instance itself. If you haven’t done so already, verify that Nginx is running on your EC2 (or in the container) and that the port is accepting traffic. root@*****:/var/discourse# ps aux | grep -i nginx root 3337 0.0 0.0 12944 876 pts/1 S+ …

Do you mean telnet to the standard port? That won’t get through with the rules as I have them. I was trying telnet <ip> 443 You should be able to telnet to port 80 (for http) and port 443 (for https) (and you need a rule for outbound too, I used all traffic 0.0.0.0/0) Yes, these are my exa…

[Bild] 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

Discourse instance unreachable on AWS

Product Support

JagWaugh (Andrew Waugh) 31. Dezember 2016 um 17:24 2

Have you set your security group to allow inbound https?

I’ve only just started with AWS… I think the user interface could be a bit less fragmented than it seems to be.

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

Discourse instance unreachable on AWS

Verwandte Themen