After updating via the gui this morning, the site is down. Seems like it tried to update from Postgres V15 to V18, but failed. So I rebuilt from within the app via launcher, no help. Also a complaint about VIPS /usr/local/lib/libvips.so.42 Any ideas or is it just me?

It’s always worth trying a second rebuild, especially with a database version bump. See the nearby topic [imagem] PostgreSQL 18 update for self-hosters ./launcher rebuild app If you still have trouble, please paste 100 lines or so of the output that you saw, preferably in a code block. As C…

[imagem] PostgreSQL 18 update for self-hosters ./launcher rebuild app I did try that but of course did not see the thread you mention. I had made a backup before I started the update. So I was able just now to get it working by manually updating to PG V18 within the container, and also insta…

interesting that I already have in the app.yml file from Oct 2025: templates: “templates/postgres.template.yml” Am I reading something incorrectly from the other topic?

I think that means you have the default choice, which is not to pin postgres to a particular version, but take whatever Discourse likes. (People will pin a particular version when they see the new version coming and want not to take it. But they need to act before it arrives unexpectedly.)

OK, sigh, so I am not sure then what went wrong with my update this morning, why it failed. I am leery of upgrading the other site until I understand why this site failed, as I do not want to repeat the failure, especially since I am not fond of manually upgrading things within the container as I d…

My guess is that this update, from today, which introduces the version 18 of postgres, will need two rebuilds. From the web interface it’s only possible to do one rebuild, and if I’m right about that, a web interface update will always appear to fail. In fact, it didn’t fail, but only went half way…

Right, good idea on cli update instead of gui. The first site is on Ubuntu 22.04, the second site that I still need to upgrade is on 24.04. I had enough excitement this AM, when I try the second site from cli update alone, I will report back. I still see the old vips on the second server /usr/loc…

OJ just to be clear, my first discourse update definitely failed. even after a cli rebuild post gui update. Sooo, I had to manually update the containers to V18 of both Postgres and vips. I am hoping for a better outcome on the second site Stay tuned.

That is a pretty bad situation.

make sure you have enough disk space. Take note in the other topic that is recomended for 2 x database size

A última atualização desta manhã (03/08/2026) quebrou meu Discourse, é só comigo?

Suporte

sandra.mccollum Agosto 3, 2026, 6:22pm 14

OK, pela CLI no Servidor 2, funcionou. Que coisa. Acho que a lição é usar a CLI para atualizar. Obrigado, Ed_S

Tópico		Respostas	Visualizações
Site Offline Since Update - pg15 upgrade failed Bug	11	398	5 de Fevereiro de 2025
PostgreSQL 18 update for self-hosters Announcements	46	858	10 de Agosto de 2026
Upgrade failed spectacularily Support	25	906	10 de Fevereiro de 2025
Site offline after rebuild (4th Feb 2025) Support	16	506	6 de Fevereiro de 2025
Update “3.4.0.beta4” failed Self-hosting	10	333	8 de Fevereiro de 2025

A última atualização desta manhã (03/08/2026) quebrou meu Discourse, é só comigo?

Tópicos relacionados