Hi I am having trouble rescuing a failed upgrade on a Ubuntu 20.04.5 LTS (Focal Fossa)" local machine. Following the failed update, from the command line I ran first sudo apt-get update sudo apt-get upgrade cd /var/discourse git pull sudo ./launcher rebuild app the last part of the output was - …

Hello and welcome @Nanovitruvius :slight_smile: There have been a couple of reports of failed upgrades in the past hour or so, and a couple of fixes have now been put in place for those which seemed to have worked for most. :+1: The error "alter schema public owner to discourse;" in your second co…

It looks to me like this is the important part - the ownership of a file is wrong, somehow: [image] Nanovitruvius: I, [2022-11-24T17:05:57.565221 #1] INFO -- : > sleep 5 2022-11-24 17:05:57.591 UTC [42] FATAL: private key file "/etc/ssl/private/ssl-cert-snakeoil.key" must be owned by the data…

[image] Nanovitruvius: WARNING: Docker version 17.05.0-ce deprecated, recommend upgrade to 17.06.2 or newer. That version of docker is more than five years old. I would strongly recommend you look to upgrade it while you’re taking care of the other points raised above.

Thank you so much for your swift replies! @JammyDodger - I have increased the relevant line to 10 s, but still get the same issue now as before (it always returns with the Fatal SSL certificate. @Ed_S I have checked the ownership of the file as you suggested, but it seems identical to yours (excep…

I’ve now upgraded docker to the latest version, the error still looks the same. During the upgrade I got some permission errors (it still seems to work ok): sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin Reading package lists... Done Building dependency tree …

I’ve now tried with sleep 10 and sleep 60 but both give the same output (except the INFO – : > sleep 60 line)

[image] Nanovitruvius: @Ed_S I have checked the ownership of the file as you suggested, but it seems identical to yours (except the dates): It looks like you might be checking the file on the host: you need to enter the app and check it within there.

Mea culpa, and you’re right here the permissions seem to be quite wrong: root@nano-app:/var/www/discourse# sudo ls -l /etc/ssl/private/ssl-cert-snakeoil.key sudo: /etc/sudo.conf is owned by uid 1000, should be 0 sudo: /etc/sudo.conf is owned by uid 1000, should be 0 sudo: error in /etc/sudo.conf, l…

That looks like a different thing: you’re already root, so you don’t need sudo in this case, so these errors needn’t be a bother. What kind of installation are you trying to upgrade: is it a standard installation?

Standard installation, don’t think we have any plugins (its a long time since I installed), its on a local machine, and fairly small (500 MB or so Backup) I checked again without sudo and the owner is discourse: root@nano-app:/var/www/discourse# ls -l /etc/ssl/private/ssl-cert-snakeoil.key -rw-r--…

Failed web upgrade

Product Support Self-hosting

Ed_S (Ed S) November 25, 2022, 7:22pm 14

Hmm, sorry, no more ideas at present.

As a last resort, one does see advice to take a backup, start a fresh install, and restore the backup. I’ve never done this myself!

Topic		Replies	Views
Upgrade failed spectacularily Product Support	25	1174	February 10, 2025
Failing update Self-hosting	32	1076	August 26, 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2392	November 26, 2021
Bootstrap failure during most recent upgrade Self-hosting	6	687	February 3, 2023
Discourse shell update is failing constantly Self-hosting	3	981	June 21, 2020

Failed web upgrade

Related topics