Update UI not fixed after update error and SSH launcher rebuild

Product Support Self-hosting

AI-generated summary

aschrijver reported an issue on two self-hosted Discourse forums where a UI update failed, leaving the Update UI stuck displaying an error message that requested an SSH launcher rebuild, even after successfully running ./launcher rebuild app via SSH. Ed_S advised the user to perform the rebuild a second time and check the logs. After repeating the process, aschrijver confirmed the issue was resolved, noting that they did not provide logs since the fix worked. Ed_S suggested that needing a second rebuild likely occurred because the database version changed earlier in the year, and the user’s instance was only now picking up that change.

1

I have 2 self-hosted discourse forums on 2 separate VPS’es. They were nearly up-to-date with latest, but not exactly on the same version. Last week I tried to update them via the Update UI. For both forums this resulted in an error in the Discourse (not the docker_manager) install process, and the updates did not succeed. After that the Update UI showed as follows:

Update UI says "You are running an old version of the Discourse image" and requests a launcher rebuild app via SSH.
Update UI says "You are running an old version of the Discourse image" and requests a launcher rebuild app via SSH.1184×610 36.4 KB

No problem. I went into SSH and updated both via ./launcher rebuild app and that worked like a charm… I thought. But not quite. Both forums are now at 2026.11.0-latest.

When I go to the Update UI on either forum the regular UI chrome is not showing, and it is still showing the above message, requesting SSH update. I expected the UI to be working, alllowing UI-based updates again.

(Unfortunately I do not have logs to attach on the update errors. I also did not yet do the rebuild app for the second time in a row, wanted to report this first.)

2

Do the second one, and then paste the last 1000 lines of the console output.

3

Running for the second time fixed it. Thank you @Ed_S (I had trouble getting the logs from my VPS, omitting since it works now)

4

The most likely reason to need a second update is if the database version changed, which it did, earlier this year. Perhaps you just picked up that change.