Hello, I currently have Discourse installed on a droplet in DigitalOcean, however, after the setup, when navigating over to the website to register my admin account, it says that the server refused to connect. I also checked my firewall settings but my firewall is disabled. When I used the open port checker, it says ports 80 and 443 are closed. It seems like all ports are closed except port 22 (ssh). I am a bit confused since if those ports were closed, then the setup would’ve alerted me about that. Does anybody have a fix? Thanks.
AI-generated summary
KhoiUSA reports that after installing Discourse via DigitalOcean’s 1-click app, ports 80 and 443 are closed (only port 22 is open), preventing website access despite a successful setup. They confirm the firewall is disabled, sharing sudo ufw status output showing no active rules 230341/3. itsbhanusharma asks whether the install was manual or via 1-click, and RGJ clarifies that since it was a 1-click install, support must be sought from DigitalOcean — Discourse only supports the official Docker installation. pfaffman suggests a possible DNS misconfiguration, noting the standard installer performs port checks during setup. JammyDodger references a prior case where users resolved similar issues by abandoning the 1-click installer and switching to the standard Docker method, recommending this path forward. The consensus is that 1-click installs are unsupported here, and users should migrate to the official method for reliable configuration and support.
Hi @KhoiUSA
Did you install discourse yourself or used DigitalOcean 1 click app?
Could you ssh into the terminal & share the output of command
sudo ufw status
Yes, I did use the DigitalOcean 1 Click App. Attached below is the output of sudo ufw status.

I am sorry, if you used the DigitalOcean 1-click app then you should go to DigitalOcean support if you have any issues.
We can only support the official Docker installation here.
It’s probably that you have your DNS wrong, but the standard install will do a test when you run discourse setup.
This has cropped up previously, eg:
In that case they had a much easier time moving away from the one-click installer, and following the standard install guide instead. ![]()