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)

./launcher rebuild app-Befehl nicht gefunden

Unterstützung Installation

pfaffman (Jay Pfaffman) 9. September 2019 um 23:43 6

Aha! Anscheinend lässt es die Konsole laufen, und du hast vergessen, dass du den Container betreten hast (mit ./launcher enter app).

Thema		Antworten	Aufrufe
Sorry there was an error upgrading Discourse Support	5	740	20. März 2021
Cannot upgrade due to old version of docker Self-hosting	4	1682	19. Juni 2018
Beta update to 2026.1 Self-hosting	15	303	19. Februar 2026
Upgrade failed - could use some help to try and fix using SSH Support	17	1691	4. November 2020
./launcher rebuild app for old 1.6 discourse not working Self-hosting	12	949	25. Januar 2023

./launcher rebuild app-Befehl nicht gefunden

Verwandte Themen