2 months ago
Hi. For almost 24h hours I'm asking Reailway team for a help but without success. Only I hear it's an application issue (I'm pretty sure it's not) but I cannot go forward.
I created few applications which have it's own databases (postgres).
On staging everything works ok.
I created new mirror environment (production) from stagging.
And all service which uses postgres worked once (migrations were created). But then stopped to connect to the database.
One interesting service is Temporal (so it's not my application bur ready docker image). After redeployment it has connections issues:
2026-03-18T18:26:58.347Z [31mERROR[0m sql handle: unable to refresh database connection pool {"error": "unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: password authentication failed for user \"postgres\" pq: password authentication failed for user \"postgres\"]", "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/common/persistence/sql/sqlplugin/db_handle.go:105"}
2026-03-18T18:27:00.083Z [31mERROR[0m Unable to create SQL database. {"error": "no usable database connection found", "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/sql/handler.go:69"}
Env vars for service are set using Railway env vars (internal database connection).
4 Replies
2 months ago
Similar here https://station.railway.com/questions/db-timeouts-73d5ef82
Everything fine until about an hour ago...
2 months ago
Unfortunately it worked for me... after reainstalling whole environment again
patrykomiotek
Unfortunately it worked for me... after reainstalling whole environment again
2 months ago
Stood up Supabase today. Testing it out. But the do have us w their offering....
2 months ago
Hi Patryk, glad you got it working by reinstalling the environment. The "password authentication failed" error typically happens when mirroring an environment, the database service gets fresh credentials, but the env var references may still resolve to the old values. Reinstalling ensures everything is in sync.
For future reference, after mirroring an environment, check that the DATABASE_URL and related variables are pointing to the new environment's database credentials, not the source environment's.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago
