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…

Here’s my last idea. chmod -r 101.104 /var/discourse/shared/standalone/postgres_data Then rebuild

I ran the command git suggested but it seems to be failing for the same reason [image]

[Bild] 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, y…

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.

Willkommen bei nginx! Seite vor dem Neuaufbau, Site lässt sich jetzt nicht neu erstellen

Unterstützung

pfaffman (Jay Pfaffman) 1. Juni 2025 um 23:09 5

Ja, Sie können Move a Discourse site to another VPS with rsync folgen und dann herausfinden, welche uid und gid Sie in den Datenbankdateien benötigen.

Thema		Antworten	Aufrufe
After i rebuild get below error return #<Process::Status: pid 1631 exit 1 Support	4	171	27. Dezember 2024
ArgumentError: directory for pid=/.../unicorn.pid not writable Self-hosting	43	2219	9. Oktober 2023
Discourse build is broken due to removed file? Development	11	1992	16. Oktober 2017
Building bootstrap error Self-hosting	46	2125	20. Dezember 2022
Unable to boostrap Discourse since last upgrade Self-hosting	5	718	22. Januar 2023

Willkommen bei nginx! Seite vor dem Neuaufbau, Site lässt sich jetzt nicht neu erstellen

Verwandte Themen