I had a drive fail on me so I copied it all to a new one and some permissions broke. Discourse is now refusing to run and I’m not sure why. Here is the discourse-doctor output: pyx@localhost:~/discourse_docker$ sudo ./discourse-doctor DISCOURSE DOCTOR Sun Jun 1 02:58:54 PM EDT 2025 OS: Linux loca…

[圖片] darkpixlz: detected dubious ownership in repository at '/var/www/discourse' To add an exception for this directory, It looks like the new container has different user ids than the old one. If you have a backup, it’s easier to start with an empty database and do a restore. Otherwise, you…

I don’t believe I have a backup for the site is the only issue with that plan. Is there any way to restore the site content / make a backup without a running app? I am planning on putting Proxmox on this server now which should fix a lot of that.

Yes you can follow Move a Discourse site to another VPS with rsync and then figure out what uid and gid you need in the database files.

Thanks, will check up on that after I get Proxmox working properly.

It failed the first rebuild: I, [2025-06-02T04:21:14.919144 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all' I, [2025-06-02T04:21:17.451801 #1] INFO -- : discourse-ai is already at latest compatible version discourse-chat-integ…

From earlier output, I’m fairly certain this is because of permissions as I (sort of) described above.

To me it looks like postgres is missing but that wouldn’t make sense because I thought discourse-setup installed it for you.

Right. It’s in the container. You do have the postgres template, right?

I’m not sure what that is. So far what I’ve done is followed the tutorial you linked, cloned the discourse-docker repo & the old app.yml file, and tried a rebuild.

If you used discourse-setup then you should have the postgres template. You do have that address in use error. Are you sure that you don’t have another postgres running? Is this an empty VM or something else?

欢迎来到 nginx! 重建前的页面，站点现在无法重建

支持

pfaffman (Jay Pfaffman) 2025年六月2日 18:35 14

这是我的最后一个想法。

chmod -r 101.104 /var/discourse/shared/standalone/postgres_data

然后重建

Upgrading from a very old container fails due to postgres permission errors

話題		回覆	觀看
After i rebuild get below error return #<Process::Status: pid 1631 exit 1 Support	4	237	2024年十二月27日
ArgumentError: directory for pid=/.../unicorn.pid not writable Self-hosting	42	2803	2023年九月9日
Discourse build is broken due to removed file? Development	11	2086	2017年十月16日
Building bootstrap error Self-hosting	45	2625	2022年十一月20日
Unable to boostrap Discourse since last upgrade Self-hosting	4	812	2023年一月22日

欢迎来到 nginx! 重建前的页面，站点现在无法重建

相關主題