Hello, When I tried making an instance on AWS and connected it all correctly, my instance is timing out, not allowing me to connect to it. [image] The website is https://test.darkpixlz.tk, and the server claims it’s running. [image]

What did you do to make the server available externally? Did discourse-setup do the connectivity check, or did you bypass it?

I’m running the public IP through Cloudflare to access through the domain, and yes it passed.

So you set up specific access rules for 80 and 443?

No, was never made aware on how to do that. I just have an A record pointing to the server’s IP. [image]

So what happens if you switch it to “DNS only”? Does it start working then?

When I was doing that I was getting my browser’s “Connection Timed Out” screen.

Yeah, it’s definitely connecting, because when I went to rebuild it says the server is down which si correct, but when it goes it it just times out. [image]

That just means Cloudflare can’t contact an upstream server. Turn off the orange cloud.

Connection is timing out

Product Support Self-hosting

Falco (Falco) October 8, 2022, 9:17pm 8

Have you configured the EC2 instance security group in order to allow ingress traffic on the ports 80/443?

Topic		Replies	Views
AWS connection has timed out Self-hosting	7	776	March 20, 2020
ERR_CONNECTION_TIMED_OUT when trying to connect to a discourse instance hosted on Cloudflare Tunnels Self-hosting	0	63	April 7, 2026
Discourse instance unreachable on AWS Product Support	27	4372	February 8, 2017
The connection has timed out Self-hosting hosting	11	3580	January 13, 2018
Connection timed out while connecting to upstream on AWS Self-hosting hosting	12	4050	June 28, 2016

Connection is timing out

Related topics