24 days ago
Hello, I cannot login into postgres with password that worked after volume increase.
I had pre build n8n with worekrs and everything was working until postgres was full. I increased volume and now my worker n8n cannot connect to postgres
There was an error initializing DB
password authentication failed for user "railway"
2025-08-14 07:39:39.301 UTC [31] DETAIL: Connection matched file "/var/lib/postgresql/data/pgdata/pg_hba.conf" line 128: "host all all all scram-sha-256"
2025-08-14 07:39:42.097 UTC [32] WARNING: database "railway" has a collation version mismatch
2025-08-14 07:39:42.097 UTC [32] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-08-14 07:39:42.097 UTC [32] 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-08-14 07:39:46.074 UTC [33] FATAL: password authentication failed for user "railway"
2025-08-14 07:39:46.074 UTC [33] DETAIL: Connection matched file "/var/lib/postgresql/data/pgdata/pg_hba.conf" line 128: "host all all all scram-sha-256"
I tried to connect via Railway CLI but after my railway connect comand im keep receiving Proxy tcp error: connectio url should point to the railway tcp proxy error railway postgres connect problem
Please help since i crashed whole system
5 Replies
24 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Railway
Hey there! We've found the following might help you get unblocked faster: - [🧵 password authentication failed for user "postgres"](https://station.railway.com/questions/password-authentication-failed-for-user-2c51edb9) - [🧵 Changed my postgres to metal and lost my data](https://station.railway.com/questions/changed-my-postgres-to-metal-and-lost-my-8511aed6) - [🧵 FATAL: password authentication failed for user "postgres"](https://station.railway.com/questions/o-h-engine-jdbc-spi-sql-exception-helper-5ade7840) If you find the answer from one of these, please let us know by solving the thread!
24 days ago
Nothing that could help me
23 days ago
This isn't a password issue but a DB version mismatch:
2025-08-14 16:42:16.342 UTC [1015] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
All you did was resize the volume?
Status changed to Awaiting User Response Railway • 23 days ago
22 days ago
We have the same collation mismatch of 2.36 vs 2.41 since a Postgres redeploy 2025-08-14, interested in the cause / solution as well.
22 days ago
The DB version mismatch issue is that the Railway PostgresSSL image does not specify / allow configuring the debian version tag. And the base Postgres version changed the default/latest version to trixie. See https://github.com/railwayapp-templates/postgres-ssl/blob/main/Dockerfile.16 and https://github.com/docker-library/postgres/issues/1356