User eazoppe encountered an error Port 443 of compute r does not appear to be accessible while setting up Discourse on DigitalOcean using the one-click installer, despite using CloudFlare for DNS and pointing the domain to their DigitalOcean IP. IAmGav initially suspected the domain wasn’t pointing to DO, but eazoppe confirmed it was. After IAmGav asked for the URL, eazoppe shared https://forum.rankerprobot.com/. IAmGav then advised checking CloudFlare’s A records, noting traffic wasn’t reaching DO. eazoppe insisted no blocking was in place. Steven clarified that while the domain pointed to CloudFlare IPs (indicating correct NS setup), an A record for the subdomain forum.rankerprobot.com pointing to the DigitalOcean droplet’s IP was required. eazoppe confirmed they had already added this record but still faced the error. Finally, IAmGav pointed out the Proxy Status in CloudFlare should be set to “DNS only” — not proxied — to allow direct traffic to DO. Following this, eazoppe confirmed the setup worked and thanked the helpers. The issue stemmed from CloudFlare’s proxy interfering with direct port 443 access to the DigitalOcean server.
Okay so I am trying to setup my own Discourse forum on DigitalOcean using the one click system but when I get to which domain I should set it up on, I just keep getting the error of Port 443 of computer does not appear to be accessible.
I am using CloudFlare for my DNS and I have searched and tried everything and have kept getting the same error over and over again. Would someone please assist me?
your domain is not pointing to DO.
That is why you getting that error
It is though.
I set my Domain to go to my DigitalOcean public IP.
what is the url you going to use ?
check you A records on cloudflare.
its not allowing the traffic to DO
It’s not blocking anything. So it should be allowing the traffic to DO.
The domain points to cloudflare ips. Which is signs that the ns servers are well configured.
But on cloudflare, you need to add an A record on the subdomain : forum(.rankerprobot.com), with the ip of the digitalocean droplet as a target.
I did do that and I am receiving the same error that I was getting before.
Proxy Status should be set to DNS only.
There we go, it worked. Thank you for your help.