Same issue here, I restarted my Postgres and it's not getting back online!

Same I got a ton of clients!

Same here

Same here, can't connect to MySQL. Major disruption on our side.

n8n log:

Initial database connection attempt 3 failed: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable..

It is stressing me out i got a ton of clients. Is there an official update?

Any logs on the Postgres service?

2026-08-29 00:51:42.000 UTC [132] 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.

2026-08-29 00:51:42.006 UTC [131] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:42.006 UTC [131] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:42.006 UTC [131] 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.

2026-08-29 00:51:42.288 UTC [133] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:42.727 UTC [134] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:42.727 UTC [134] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:42.727 UTC [134] 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.

2026-08-29 00:51:42.814 UTC [135] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:42.814 UTC [135] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:42.814 UTC [135] 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.

2026-08-29 00:51:42.850 UTC [136] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:42.850 UTC [136] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:42.850 UTC [136] 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.

2026-08-29 00:51:43.842 UTC [137] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:43.842 UTC [137] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:43.842 UTC [137] 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.

2026-08-29 00:51:44.104 UTC [138] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:44.104 UTC [138] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2026-08-29 00:51:44.104 UTC [138] 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.

2026-08-29 00:51:44.122 UTC [139] WARNING: database "railway" has a collation version mismatch

2026-08-29 00:51:44.122 UTC [139] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

How are you connecting to your database? Through the private network or public?

In my application (n8n) Private railway internal...

I can connect to the database externally through a proxy, the problem is to connect in n8n. Should I refresh de index and the COLLATION VERSION as indicated in the warning?

Could you try re-deploying n8n? It could be holding onto connections at start-up so the stale connection never dies.

Its working after a restart. Thanks!