Discourse version at community.gasturbinesupport.com: NOT FOUND

AI-generated summary

The user qasimala encountered issues with a Discourse installation on a DigitalOcean droplet, where the site was inaccessible and discourse-doctor reported the Discourse version as NOT FOUND. justin identified the one-click install as unsupported and advised reinstalling using the official guide. After a manual reinstallation, the version was detected, but the site still failed to load with a ‘connection reset’ error. itsbhanusharma suggested a possible DNS propagation delay, and qasimala thanked the community for the help.

What I’ve Done:
I have set up a 2 GB droplet on DigitalOcean, have forwarded the domain to digitalocean using the nameservers, have added an A record in digitalocean for the subdomain, and installed the oneclick version of discourse on the droplet.

I have set up the mailgun server and tested it using discourse-doctor and it delivers the email as expected.

The Problem
Nothing comes up when I search the subdomain. When I ran the discourse-doctor from /var/discourse, this comes up:

Discourse version at community.gasturbinesupport.com: NOT FOUND
Discourse version at localhost: NOT FOUND

Possibilities:

There is another user with a similiar problem here. His problem had to do with the ssl cert but I’m not sure how to disable the SSL .

Thanks for helping.

Unfortunately this is an unsupported install method.

Please use our discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub to reinstall.

Thank you for the quick reply. I destroyed that droplet and created a new one. Went through the whole setup manually as detailed in the guide. Now when I run discourse-doctor it shows discourse version at community.gasturbinesupport.com: discourse 2.4.0.Beta10 and discourse version at localhost: discourse 2.4.0.beta10.

However, When I actually go to the link, it throws an error: this site cant be reached. The connection was reset.

What are my next steps in diagnosing the problem?

Thanks for the help.

It’s loading fine for me… Seems like a DNS issue at your end, maybe wait a couple hours then retry the link?

Thank you so much. Really appreciate it.