a month ago
I am unable to access n8n since yesterday. I have checked the Railway account, the Workers seem to be working perfectly but when I checked the logs, it is all red.
See sample logs below: 2025-10-22 20:39:50.708 UTC [5074] WARNING: database "railway" has a collation version mismatch
2025-10-22 20:39:50.708 UTC [5074] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-10-22 20:39:50.708 UTC [5074] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-10-22 20:40:11.035 UTC [5075] WARNING: database "railway" has a collation version mismatch
2025-10-22 20:40:11.035 UTC [5075] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-10-22 20:40:11.035 UTC [5075] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-10-22 20:40:50.763 UTC [5076] WARNING: database "railway" has a collation version mismatch
2025-10-22 20:40:50.763 UTC [5076] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-10-22 20:40:50.763 UTC [5076] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-10-22 20:41:19.136 UTC [23] LOG: checkpoint starting: time
2025-10-22 20:41:34.415 UTC [23] LOG: checkpoint complete: wrote 153 buffers (0.9%); 0 WAL file(s) added, 0 removed, 0 recycled; write=15.245 s, sync=0.013 s, total=15.280 s; sync files=38, longest=0.012 s, average=0.001 s; distance=794 kB, estimate=4779 kB; lsn=B/7E38B0B0, redo lsn=B/7E38B078
5 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
🧵 n8n Service crashed after PostgreSQL automatic update - Collation version mismatch
🧵 WARNING: database "railway" has a collation version mismatch
If you find the answer from one of these, please let us know by solving the thread!
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 2 months ago
a month ago
Hey, you should try to run the following SQL queries to rebuild all objects and refresh the collation version as per the Postgres docs. As always, make sure to backup your database first (this can be done with pg_dump).
REINDEX DATABASE railway;
ALTER DATABASE railway REFRESH COLLATION VERSION;If this doesn't work, you can try to restore the backup to a new Postgres service and update the reference variables of your n8n service to the new Postgres service.
a month ago
I am unable to connect to the database. All attempts failed. When I created a new Postgres it crashed when trying to upload the backup database
a month ago
Please i need help. It is critical
nicetyai
I am unable to connect to the database. All attempts failed. When I created a new Postgres it crashed when trying to upload the backup database
a month ago
Please elaborate how restoring your backup crashes the new database service.