Database connection failed
Hey team I am getting an issue connecting to my new migrated postgres DB.
Project ID: 32337fdc-fe2a-42f0-a2be-bf2ec7720827
π thanks in advance
![No description](https://cdn.answeroverflow.com/1205672432573087844/Screenshot_2024-02-10_at_11.31.03_am.png)
Solution:Jump to solution
Problem solved, I had to destroy everything and recreate new db and volume.
15 Replies
Project ID:
32337fdc-fe2a-42f0-a2be-bf2ec7720827
Info when I try to CLI connect:
psql: error: connection to server at "monorail.proxy.rlwy.net" (35.213.165.89), port 56612 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
firstly can you show a screenshot of your railway project so i know whats going on
![No description](https://cdn.answeroverflow.com/1205707071266234438/Screenshot_2024-02-10_at_1.49.21_pm.png)
can you try re-deploying the database
I did - same issue
I also tried restarting
I also made sure the port for the proxy was the same as the db port
show me the public networking section please
![No description](https://cdn.answeroverflow.com/1205730733960724541/Screenshot_2024-02-10_at_3.23.23_pm.png)
that's wrong, you should set the proxy to port 5432
Same message:
psql: error: connection to server at "monorail.proxy.rlwy.net" (35.213.165.89), port 16989 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
See screenshot of my new settings
![No description](https://cdn.answeroverflow.com/1205739281440706580/Screenshot_2024-02-10_at_3.57.15_pm.png)
redeploy?
psql: error: connection to server at "monorail.proxy.rlwy.net" (35.213.165.89), port 16989 failed: FATAL: password authentication failed for user "postgres"
connection to server at "monorail.proxy.rlwy.net" (35.213.165.89), port 16989 failed: FATAL: password authentication failed for user "postgres"
@Brody Is this because maybe the old volume was attached to the new DB?
if you're passing volumes around then you've likely broken something
Solution
Problem solved, I had to destroy everything and recreate new db and volume.
makes sense