The discussion revolves around issues with the Discourse installation process on a Debian server. pablostarter encountered a problem where the ./discourse-setup script only asked for the SMTP password and Let’s Encrypt email, but not other necessary configuration values. itsbhanusharma suggested checking the containers/app.yml file and configuring the values manually or following the recommended guide using Ubuntu.
pablostarter discovered that the issue was due to missing dependencies for Postgres, which were not installed by the script. After manually installing the dependencies, the installation process proceeded successfully.
itsbhanusharma noted that the ./discourse-setup script is known to work best with Ubuntu 16.04 and may not behave as expected on other Linux distributions. pfaffman acknowledged the issue and plans to investigate further, suspecting that recent changes may have caused the problem.
I’m trying to install Discourse in a Debian server following the 30 min install guide but when I run:
./discourse-setup
I only get asked about the SMTP password and an email for Let’s Encrypt. After I type them I get an error:
Checking your domain name . . .
WARNING:: This server does not appear to be accessible at 443:443.
A connection to http://443 (port 80) also fails.
Does this look right?
Hostname :
Email :
SMTP address :
SMTP port :
SMTP username :
SMTP password : kbhgvcfxcfgvhjdi87654h3gf5d67sujwh //Some fake api
Let's Encrypt : some@email.es
And of course, they are not right, because they are blank!
I was expecting the initial script to create that file for me.. apparently it did not.
I tried to manually change the values and run ./launcher rebuild app this return an error of Docker trying to update postgres.
After some digging I found out that the problem was that some dependencies of postgres were not installed on the system. I installed them and started the installation process again, now looks that is working.
The ./discourse-setup script is supposed to install all the packages and their dependencies on it’s own but the word of caution is that it is known to work best with ubuntu 16.04.
I haven’t personally tried to install it on a host running on debian or any other linux distro so I’m not very sure about how it behaves across platforms.