Install Discourse Docker on Ubuntu 11

Support Self-hosting

AI-generated summary

The discussion revolves around installing Discourse Docker on Ubuntu 11. ITAS-Isti initially claimed that it’s difficult or impossible to install Discourse on Debian 11, but Falco corrected this, stating that it works fine if the official install guide is followed.

ITAS-Isti encountered issues with the installation, including errors with the ./launcher logs app command and the default activated cert causing a LETSENCRYPT_ACCOUNT_EMAIL change failure. Despite resolving the error by adding a mail address to the config, they were still unable to access Discourse.

After some troubleshooting, ITAS-Isti found the solution by deactivating two lines in the config related to SSL certificates. pfaffman suggested that the issue might have been caused by hitting Let’s Encrypt’s rate limit and recommended re-activating the lines and rebuilding in a week to enable HTTPS.

1

Hi,

as I know it is pretty difficult / not possible to install Discourse on Debian 11.
I have managed it to install on 10.5, but now, no matter how I try no access in the webGUI and no mail after the build-process.

I have tried more tutorials e. g. this one: https://www.arubacloud.com/tutorial/how-to-install-discourse-with-docker-on-ubuntu-18-04.aspx

Can somebody confirm if it is anyhow possible to access Discourse after install process?

Docker Container is active and also ./discourse-setup run thru …

launcher seems not to work:

./launcher logs app gives an error.

Any idea?

I.

2

Have you tried following How to install Discourse in production. As long as you can install Docker, Debian <anything that works> should work just fine.

EDIT: I assumed you meant a production install. But perhaps I’m wrong.

3

i would suggest you follow the below instead of the url you provided

4

Thank you for your answer …

According to the log teh error has been caused by the default activated cert:

LETSENCRYPT_ACCOUNT_EMAIL change failed.
letsencrypt.ssl.template.yml enabled
Unfortunately, there was an error changing containers/app.yml

It is however not activated in the yml file:

image
image745×465 91.3 KB

Is there any other configuration where the SSL certificate could be deactivated?

After adding a mailaddress as lets Encrypt Mailadress to the config the rebuild process went thru.
Despite of it I cannot access Discourse …

5

That is not true, Discourse in Debian 11 works just fine provided you can follow the official install guide.

6

I have finally found the two lines in the configs which have to be deactivated. (as still do not have a certificate to actively use.)
After rebuild I can access Discourse.

7

You probably ran it a bunch of times so that you hit let’s encrypt’s rate limit. I recommend that in a week you re-activate those lines and rebuild so that you’re HTTPS enabled. Some things won’t work without https.