NOTE: Original post updated 11/25/21 PM EST with new information Notified of critical security updates to my Discourse installation I attempted to update my installation using the Web UI (/admin/upgrade) as I have done in the past. There were two pieces of software that needed to be upgraded—Docker…

Following Michael’s advice in the above post, I commented out a plug-in in the app.yml file that was from an initial attempt at SSO authentication using the VK plug-in (we never went with this implementation but obviously forgot to remove the plug-in from the app.yml file). ## Plugins go here ## se…

How about restart? From here [изображение] The launcher command in the /var/discourse folder are not self-explaining installation I had to change and reload the configuration a couple of times for troubleshooting Siteground mail service. There are multiple bits of advice…

This update requires the docker to be restarted. So, yes your discourse is gonna be offline while you run ‘./launcher rebuild app’ in then command line. All will be 100% once the rebuild is completed.

@IAmGav Docker appears to be running. [image] @rmccown ZSm8WzJ7gLigPd08D4tiwt.png) I will try some of the other launcher commands to see if I can get things up and running.

@IAmGav Ran ./discourse-doctor and it also confirmed that Docker container is running. ==================== DOCKER INFO ==================== DOCKER VERSION: Docker version 20.10.11, build dea9396 DOCKER PROCESSES (docker ps -a) CONTAINER ID IMAGE COMMAND CREATED STA…

@rmccown Tried both start and restart without luck. [image] Still get this at the URL. [image] Running sudo ./launcher rebuild app again fails with these messages (currently looking through the file for earlier error messages). [image]

When all else fails - have you tried unplugging it and plugging back in? :wink: Reboot the instance: reboot now Bring the instance up to latest: apt-get update and apt-get dist-upgrade Then run the Discourse upgrade.

@omarfilip That’s the first thing I tried :wink: I just tried a reboot again (no Ubuntu 18.04.6 components to upgrade from earlier upgrade). [image] Same results - 502 Bad Gateway error at URL. But thanks for the suggestion.

Also just found this from November 2020 - Upgrade ends with FAILED TO BOOTSTRAP . But I have to admit I don’t know exactly what it means to “follow our default release channel.” I assume that upgrading via the Web UI is the “default release channel.”

That would be “tests-passed.” If you have not modified this line in your app.yaml file, then you are on the default release channel: ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed

[изображение] billmaya: [image] image2400×396 67.2 KB can you share the whole log, this is not enough to see the actual error.

Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance

Поддержка Самостоятельное хостинг

rmccown (Bob McCown) 25.Ноябрь.2021 17:00:26 2

How about restart? From here

Тема		Ответов	Просм.
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	325	09.08.2025
Discourse upgrade error "FAILED TO BOOTSTRAP" Support	15	1951	13.02.2022
"Waiting for unicorn to reload", then update stops Support	30	4635	20.06.2021
Latest site upgrade not working Self-hosting	11	1759	22.02.2022
Upgrade failed spectacularily Support	25	645	10.02.2025

Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance

Связанные темы