How exactly? I also set up a brand new Digital Ocean droplet, cloned the repo, ran setup, and get the 443 error.
I see this:
root@lume-community:/var/discourse# sudo ufw allow 80
root@lume-community:/var/discourse# sudo ufw allow 443
root@lume-community:/var/discourse# sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup
root@lume-community:/var/discourse# sudo ufw status
Status: active
To Action From
-- ------ ----
443 ALLOW Anywhere
80 ALLOW Anywhere
443 (v6) ALLOW Anywhere (v6)
80 (v6) ALLOW Anywhere (v6)
and then
root@lume-community:/var/discourse# ./discourse-setup
The configuration file containers/app.yml already exists!
. . . reconfiguring . . .
Saving old file as app.yml.2025-03-17-074439.bak
Stopping existing container in 5 seconds or Control-C to cancel.
x86_64 arch detected.
app was not started !
./discourse-doctor may help diagnose the problem.
Found 2GB of memory and 1 physical CPU cores
setting db_shared_buffers = 256MB
setting UNICORN_WORKERS = 4
containers/app.yml memory parameters updated.
Hostname for your Discourse? [discourse.example.com]: lume.community
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: lume.community.
WARNING: Connection to http://lume.community (port 80) also fails.
......
Can the setup script be updated to fix this (like how it automatically fixes the lack of a swap file on small-memory machines)?