User koltl is struggling to access their Discourse installation across multiple cloud providers (AWS, DigitalOcean, OVH), despite following installation guides and ensuring firewall rules allow all traffic. Ports 80 and 443 remain inaccessible, even though Discourse appears to install without errors. Community members ariznaf, Falco, Stephen, and pfaffman suggest checking DNS configuration, verifying public IP usage, ensuring Docker containers are running (docker ps), and using official cloud install instructions. koltl confirms Discourse containers are running via docker ps but netstat shows no listening ports. DNS investigation reveals a mismatch: domain nlrp.xyz resolves to an OVH IP (158.69.62.86), not the DO IP (159.203.78.37) being used. ariznaf notes the DO IP has no DNS record. Eventually, koltl succeeds using a subdomain, suggesting the root domain’s DNS configuration is flawed — possibly due to conflicting A records or misconfigured registrar settings (now using Namecheap). pfaffman confirms root domains are supported if DNS is properly configured. steven_so suggests checking SSL setup and DNS propagation. The core issue appears to be DNS misconfiguration rather than server or firewall problems.
I spun up a free tier VM with AWS to solely run Discourse. First setup went fine, I could view the success page, but I needed to redo it as I made a mistake with setting it up. Anyway, after making a new VPS, I followed the same install steps on digitalocean and after installation with no apparent issue, I am unable to connect to the Discourse. It’s running but 443 and 80 are closed despite me allowing all traffic going in and out of the server.
So I tried to set this up on DigitalOcean and it seems like I am having the same issue. 80 and 443 seem blocked or Discourse is not running properly which it should be, no errors.
Like mentioned above, I tried on AWS and it worked one time then not again afterward. Considering their tricky firewall setup, I tried a simpler way using DigitalOcean which yields the same result. Even followed the github instructions on fresh install
So I tried setting it up with OVH, same issue, 443 and 80 are closed on the IP. I am following these steps like I have numerous times for successful installations. Really confused and curious what I am doing wrong.
May be you have a proxy installed in your virtual Linux machine?
Are you sure you are using your public IP and it is your current IP adres?
In AWS each time you stop star an instance, you receive a new public IP address.
If you want a permanent one you have to create it using elastic IPs and pay for it.
In network interfaces you can check what is the public ip of your running interface.
No proxy. I properly set up the elastic IPs. Between today and yesterday, tried installing on 3 fresh installations (DO, AWS, OVH) following the same steps I linked above.
I have a production instance running in lightsails and a test site using a free ec2 instance.
And we haven’t got this problem (well I forgot to open the amazon poxy a couple of times at first).
Followed it and still no luck. I have subdomains of the domain I am using on another VPS but that shouldn’t be an issue since the main was is forwarded to the VPS I am using. Any other things I could try?