Upgrades via the web UI are disabled until you run the latest image. To do so log in to your server using SSH and run: cd /var/discourse git pull ./launcher rebuild app I get the above screen when looking to do an update from the dashboard. My installation seems to be in var/www/di…

Can you share the exact commands you’re running, and the output you’re seeing (feel free to redact IP addresses/hostnames if you prefer)? /var/www/discourse sounds like you’re inside the docker container, rather that on your server. You should be doing something like: ssh user@forum.example.com cd…

You’re somehow connecting inside the container. You should probably connect to port 22 and maybe you’re connecting to port 2222; older installations had an ssh port exposed for the container.

I’m using Vultr and I just log into my account and open the console window. My command line shows root@vultr-app. is their a way to log out of the app?

I think i’m there I used an exit command now my folder structure looks right. Update is now rebuilding thanks for the help.

Aha! So apparently it leaves the console running and you forgot that you’d entered the container (with ./launcher enter app).

Yes that’s exactly what happened C Robert Christensen (Bob)

comando ./launcher rebuild app non trovato

Supporto Installazione

bobdude (Bob Christensen) 9 Settembre 2019, 5:56pm 5

Penso di essere arrivato. Ho usato un comando di uscita e ora la struttura delle cartelle è corretta. L’aggiornamento è ora in fase di ricostruzione. Grazie per l’aiuto.

Argomento		Risposte	Visualizzazioni
Sorry there was an error upgrading Discourse Support	5	741	Marzo 20, 2021
Cannot upgrade due to old version of docker Self-hosting	4	1682	Giugno 19, 2018
Beta update to 2026.1 Self-hosting	15	303	Febbraio 19, 2026
Upgrade failed - could use some help to try and fix using SSH Support	17	1693	Novembre 4, 2020
./launcher rebuild app for old 1.6 discourse not working Self-hosting	12	949	Gennaio 25, 2023

comando ./launcher rebuild app non trovato

Argomenti correlati