Hey posting here after trying everything and got stuck with my upgrade. I was updating the forum after many months. I ran a backup as usual and downloaded it. Apparently, in this update process, there is a migration from PG 13 to 15. Everything was running with no issues until the update failed I…

Update: I still trying things. At this point, I just want to go back to a buld that supports PG13 so I can restore my backup, but I still blocked trying that. The commit hash before the upgrade was v3.3.0.beta6 +294, im trying to re-build that one vie YML but still saying this when building up: r…

If you made a backup like you said you did, the easiest thing is to spin up a new droplet, follow Move a Discourse site to another VPS with rsync (but do not copy the database files), and then restore your backup.

[이미지] pfaffman: If you made a backup like you said you did, the easiest thing is to spin up a new droplet, follow Move a Discourse site to another VPS with rsync (but do not copy the database files), and then restore your backup. Hy [이미지] pfaffman: If you made a backup like you said you …

That’s it. See also Restore a backup from the command line

Thanks again, Jay, for responding. I really appreciate your time helping me through this nightmare. I’m trying to do it that way (forcing the version in the YML) but apparently discourse_docker is not happy (yet) with that change: FAILED -------------------- Pups::ExecError: grep -q 'outlets/befor…

[이미지] skozz: forcing the version in the YML Don’t do that. Just do a normal install of the latest version of everything and restore the database.

[이미지] pfaffman: Just do a normal install of the latest version of everything and restore the database. Understood, I will try right now. However, quick question: If the backup is from an old version of Discourse that were using PG13, will I have problems importing the backup into the latest …

Sorry @pfaffman I wrote a previous message thinking the problem was gone but then a plot twist happened. After a long time importing, I saw how the forum was online again listing all the posts and so on. In the terminal, the log was: [...] -- execute("DELETE FROM site_settings WHERE name='warn_r…

Update: Logged into the rails console, and apparently the are only 10 posts, not all the ones to be imported :thinking: /var/www/discourse# rails c Loading production environment (Rails 7.2.2.1) discourse(prod)> Post.count => 10 discourse(prod)> Post.where(“baked_version IS NULL”).count => 0 …

Sigh. Are you using the same hostname? (Maybe so?) [이미지] skozz: EXCEPTION: 903 posts are not remapped to new S3 upload URL. S3 migration failed for db 'default'. That’s your problem now. Did you configure S3 in the database or in the yml file? I guess it’s the former. The easiest thing wou…

포럼 업데이트 중 멈춤 및 PG 마이그레이션 문제

지원 자체 호스팅

pfaffman (Jay Pfaffman) 6월 12, 2025, 8:26오후 17

That’s not proper. See Configure an S3 compatible object storage provider for uploads. You want all those settings in your yml files.

글		댓글	조회수
Forum not working after update – what’s missing? Self-hosting	35	787	9월 4, 2025
Upgrade failed spectacularily Support	25	975	2월 10, 2025
Forum crashes after upgrading from 2.4.0 Self-hosting	9	1550	7월 4, 2020
Upgrading old version 2.8.5 issues Self-hosting	26	531	12월 15, 2025
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	531	7월 10, 2025

포럼 업데이트 중 멈춤 및 PG 마이그레이션 문제

Related topics