2 hours ago
My Postgres HA cluster (project: peos-production) is rejecting the password stored in its own environment variables — POSTGRES_PASSWORD, PGPASSWORD, and DATABASE_URL all show the same value, but authentication fails even connecting from inside the database's own container via its internal hostname (postgres.railway.internal), using the exact password shown by echo $PGPASSWORD in that same container. This started sometime around [today's date] — I'm not certain whether it began before or after I attempted a manual password change via the Variables tab (since the automatic 'regenerate password' button returned 'Password reset is not supported for Postgres HA clusters'). This is currently causing a full production outage — no application can authenticate to the database at all.
1 Replies
2 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 hours ago
2 hours ago
You can try to do it manually, by selecting the HA node, then go to the console tab
, from there you can run psql, then use the command ALTER ROLE postgres WITH PASSWORD '<PASSWORD>';. Use the password to update the POSTGRES_PASSWORD/PGPASSWORD variable on the original postgres node you created the HA cluster from
. Then redeploy all related services.