Error in install AWS lightsail with CloudFlare

Product Support Self-hosting

AI-generated summary

Ppantaleo is encountering an issue installing Discourse on AWS Lightsail with CloudFlare, receiving a warning that port 443 is inaccessible despite port 80 working — suggesting a DNS or firewall issue. The error message advises confirming the domain resolves to the correct IP and checking firewall settings, or manually editing containers/app.yml and rebuilding via ./launcher rebuild app. Lilly responds with links to similar issues on Discourse Meta, including port 443 not accessible via hostname and error port 443 not open. Ppantaleo confirms those threads didn’t resolve the issue. pfaffman notes the site is now up and asks if the problem was solved by turning off CloudFlare’s orange cloud proxy — a common fix for such connectivity issues. The discussion suggests the root cause was likely CloudFlare’s proxy interfering with HTTPS (port 443) traffic, which can be resolved by temporarily disabling the proxy or ensuring proper SSL/TLS settings in CloudFlare.

1

Hi, I have my domain on namecheap pointing to CloudFlare. In CloudFlare I have an A record pointing to the static ip of my instance in AWS LightSail. But when I run: ./discourse-setup

I get the error:

Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: forum.lata
rxiv.org.

SUCCESS: A connection to port 80 succeeds!
This suggests that your DNS settings are correct,
but something is keeping traffic to port 443 from getting to your server.
Check your networking configuration to see that connections to port 443 are allowed.

The first thing to do is confirm that forum.latarxiv.org resolves to the IP address of thi
s server.
You usually do this at the same place you purchased the domain.

If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for “open ports YOUR CLOUD SERVICE” might help.

This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type

./launcher rebuild app

In the web the error is 522

2

Hi @Ppantaleo welcome to Discourse Meta :wave:

hmmm, that looks similar to these topics, perhaps they can help

3

Thanks Lili, neither of the two threads reports a solution to the problem unfortunately.

4

Your site is up now, so this is solved?

Did you turn off the orange cloud as the links suggested?