I’ moving my discourse to a new vps, using Move a Discourse site to another VPS with rsync - Documentation / Self-Hosting - Discourse Meta After copying full files, launching /discourse-setup I got this error: 570:M 27 Jul 2024 14:26:52.569 # Warning: Could not create server TCP listening socket *…

I found this error PG::ConnectionBad: connection to server on socket “/var/run/postgresql/.s.PGSQL.5432” failed: No such file or directory (PG::ConnectionBad) I, [2024-07-27T14:27:02.567042 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' URGENT: Failed to in…

Tried again. Same error. Any suggestions? I moved from ubuntu 18.04 to ubuntu 24.04 found the problem on postgresql user

I would try to install with an empty database and restore it after the site is set up. I think there might be a minor version difference between your version and the new server so it doesn’t work. Another possibility is that you didn’t shut down the old server before copying the files over.

I used ./launcher stop app. Now I made a fresh install (with a different domain) Tomorrow I’ll try to change domain rebuild, modifiyng app.yml rebuild, and then restore.

[이미지] Saiano: PG::ConnectionBad: connection to server on socket “/var/run/postgresql/.s.PGSQL.5432” failed: No such file or directory (PG::ConnectionBad) I got the exact same error yesterday :frowning: Will do a fresh install and restore tomorrow

I did a fresh install with new domain name. Changed the hostname without rebuilding, copied letsencrypt directory to the new server. Then I changed my dns and did the restore. Everything worked.

So I am getting confused, lots of topics about rsync moves. I want to create a 2nd instance of my self-hosted discourse site on another VPS, with a different domain name. Can I not just create a new discourse site, make sure both sites are updated to the latest, make a backup from the original and…

It’s easier to restore a backup than to copy the raw database files. Also, if you do a restore it will change the host name automatically.

[이미지] pfaffman: It’s easier to restore a backup than to copy the raw database files. Internally we have hundreds of hours of tooling written around moving data & database files around. It’s still sometimes easier to restore a backup.

Also, by restore from a backup, I meant the backup created through the Discourse gui under Advanced → Backup. That should work to basically clone the site from one VPS to another, right? Some other topics were doing so via rsync, which feels like that should not be necessary, to me anyway.

rsync로 Discourse를 이동할 때 발생하는 PostgreSQL 문제

지원 자체 호스팅

supermathie (Michael Brown) 12월 19, 2025, 1:30오전 10

내부에서는 데이터 및 데이터베이스 파일을 이동하기 위해 수백 시간 분량의 도구를 작성해 두었습니다.

하지만 여전히 백업 파일을 복원하는 것이 더 쉬운 경우가 있습니다.

글		댓글	조회수
Move a Discourse site to another VPS with rsync Sysadmins migrations , how-to	55	8501	8월 17, 2025
Moving to New Server woes Support	16	488	3월 10, 2025
Hangs discourse and discourse restore FAILED Self-hosting	24	2241	8월 26, 2020
Update from 2.9.0 beta2 to beta4 failed (my site is down) Self-hosting	25	1977	5월 12, 2022
How to backup and restore a whole /var/discourse app folder? Self-hosting	17	5946	6월 19, 2020

rsync로 Discourse를 이동할 때 발생하는 PostgreSQL 문제

Related topics