Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: foro.caletawp.com.
WARNING: Connection to http://foro.caletawp.com (port 80) also fails.
This suggests that foro.caletawp.com resolves to some IP address that does not reach this
machine where you are installing discourse.
The first thing to do is confirm that foro.caletawp.com resolves to the IP address of this 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
it’s a DNS issue. You need to create a record type “A” with your domain and ip. If you are behind cloudflare, set it as “dns only” instead of proxied. Only during the install process.
also, see if port 80 and 443 are open. At Aws Lightsail, port 443 are not open by default.
1 Like
you need to open ports 80 and 443 in your vps.
It was already working before. What did you change? i saw 2 different domains.
1 Like
At left right now you have the orange cloud.
pfaffman@badboy:~$ doggo foro.caletawp.com
NAME TYPE CLASS TTL ADDRESS NAMESERVER
foro.caletawp.com. A IN 300s 172.67.211.93 127.0.0.53:53
foro.caletawp.com. A IN 300s 104.21.93.150 127.0.0.53:53
The other domain you sent a screen shot so I can’t copy paste to check.
1 Like
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)?
Ah! I had to restart after the ufw changes. Then it worked!
It might be nice if the discourse-setup script could detect the OS, and suggest or run the ufw commands, and then recommend to restart before trying the setup script again.