Issue with installation in an Ubuntu 22.04 VM

Hi, I’m a beginner and I’d like to try installing Discourse for a project, but I’m having trouble installing Discourse in a Ubuntu 22.04 VM. I followed the tutorial at discourse/docs/ at main · discourse/discourse · GitHub, but after completing the steps, I don’t see anything on my web browser (I get the message “This site can’t be reached”). I opted for the Brevo solution for SMTP.

Hi, welcome :wave:

Did the build process end without errors?

Do you have your DNS pointing to the server? DId you run discourse-setup? What is the URL?

Yes, DNS pointing server (I can ping with hostname), i run and use commande ./discourse-setup and url is
but sometimes I get an nginx page that displays for 2 minutes.

I have an end message :

, [2023-12-21T10:19:01.450496 #1]  INFO -- : Terminating async processes
I, [2023-12-21T10:19:01.481983 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 56
I, [2023-12-21T10:19:01.493459 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 125
2023-12-21 10:19:01.493 UTC [56] LOG:  received fast shutdown request
125:signal-handler (1703153941) Received SIGTERM scheduling shutdown...
125:M 21 Dec 2023 10:19:01.509 # User requested shutdown...
125:M 21 Dec 2023 10:19:01.509 * Saving the final RDB snapshot before exiting.
125:M 21 Dec 2023 10:19:01.515 * DB saved on disk
2023-12-21 10:19:01.553 UTC [56] LOG:  aborting any active transactions
125:M 21 Dec 2023 10:19:01.569 # Redis is now ready to exit, bye bye...
2023-12-21 10:19:01.844 UTC [56] LOG:  background worker "logical replication launcher" (PID 65) exited with exit code 1
2023-12-21 10:19:02.147 UTC [60] LOG:  shutting down
2023-12-21 10:19:02.675 UTC [56] LOG:  database system is shut down

+ /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=4 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e DISCOURSE_FORCE_HTTPS=true -e LC_ALL=en_US.UTF-8 -e LANGUAGE=en_US.UTF-8 -e -e -e -e DISCOURSE_SMTP_PORT=587 -e -e DISCOURSE_SMTP_PASSWORD=J7YKTUfxhpZBkGaN -e -e -e -h forum-app -e DOCKER_HOST_IP= --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:96:f4:e6:e7:14 local_discourse/app /sbin/boot

but docker conteiner is running :

root@forum:/var/discourse# docker ps
CONTAINER ID   IMAGE                 COMMAND        CREATED              STATUS              PORTS                                                                      NAMES
db41dedf0fc7   local_discourse/app   "/sbin/boot"   About a minute ago   Up About a minute>80/tcp, :::80->80/tcp,>443/tcp, :::443->443/tcp   app

Pinging gives me a local address, likely one that connects to a router. :thinking:

VM ubuntu ip address is, i use a IP private for testing

Unless you comment out the let’s encrypt and ssl templates it will fail because there is no certificate.

And I’m not sure if it’s possible to run without https anymore.

1 Like


It works, I followed a youtube video (, I did the step done in the video and I left the line checked (#) for the https let’s encrypt part on the app.yml file.

1 Like

Thank you for hepls

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.