User tpglitch is installing Discourse on Linode via the one-click app but encounters a “Discourse version at forum.[redacted].com: NOT FOUND” error after running discourse-setup and rebuilding. They confirm the domain is set up correctly and sometimes see Nginx’s default page, indicating the Docker container is running. Lilly suggests relevant Meta threads, but tpglitch finds them unhelpful. pfaffman suspects DNS issues or Let’s Encrypt rate limits, though tpglitch confirms no duplicate A records and resolves the issue by switching to a different subdomain. pfaffman speculates Linode’s installer may not fully integrate discourse-setup, but tpglitch clarifies that discourse-setup is indeed used — manually, if fields aren’t auto-filled during Linode setup. The root cause appears to be transient DNS or rate-limiting, resolved by changing the subdomain.
I am trying to install Discourse on linode with there one-click app
I ran through discourse-setup, and even tried rebuilding discourse!
The domain is setup correctly and I can ping it, and sometimes it says “welcome to nginx”, which is part of the docker container for discourse and not installed on the server.
The result of docker ps:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a494a72506a8 local_discourse/app "/sbin/boot" 6 minutes ago Up 6 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app
I noticed that when I ran ./discourse-doctor the last bit said:
Discourse version at forum.[redacted].com: NOT FOUND
Then likely DNS was broken at first and you retried a bunch of times and hit Let’s Encrypt’s rate llmits. ./discourse-setup tries to keep that from happening, but I guess Linode’s installer doesn’t use discousre-setup
welcome to Meta 
