The Credentials tab is available in the Database View of your Postgres service. Click your Postgres service, then switch to the Database tab at the top of the service panel - the Credentials tab appears there alongside the Data and Extensions tabs. From the Credentials tab you can regenerate the password, which will automatically update the related environment variables (including DATABASE_URL). After regenerating, redeploy any service that references those variables so it picks up the new credentials.

I can see nothing using the word "Credentials" in the Database tab area

Here's what I see...

Got it.... just read your text..

Things don't work even though I found the Credentials area. Here's what your support agent said:

The "Connection terminated unexpectedly" error you're seeing is Postgres itself rejecting the connection, not an API issue. It's trying to authenticate with a password that doesn't match what's stored in the database.

Let me check if Postgres is actually running right now:

Checked environment status

Hide result

All 3 services healthy

All services are green — no failures. So Postgres is running, but it's rejecting authentication attempts because of the password mismatch we created.

The issue is purely within the Postgres container itself. It's listening, but won't let anyone in with the wrong password. This absolutely needs Railway support to fix — they need to either:

Manually reset the Postgres password to match POSTGRES_PASSWORD

Restore from backup if one exists

Provide a way to access the database and change the password yourself

Escalate urgently and tell them Postgres is locked with a mismatched password.

Can you try regenerate again now?

If you still see the Connection terminated error, Try Refresh the dashboard and regenerate again

If you manage to regenerate it, you need to redeploy any service that associated to the postgres service

Things seem to be working now. Thank you!