a year ago
I had an app that worked ok with 2 instances, both connecting to a single database. However, out of nowhere, one instance is no longer able to connect to this database.
Error: P1001: Can't reach database server at `postgres-85ae4b46.railway.internal`:`5432`
Please make sure your database server is running at `postgres-85ae4b46.railway.internal`:`5432`.One of 2 instances connects alright and service is live with the latest commit. The other fails always, and causes the deployment state to show as Crashed.
If I press "Restart" on the container, it brings the whole service down.
1 Replies
a year ago
Hello,
Can you please go into the service settings and switch the runtime to V2.
This is a known issue on the Legacy runtime, hence it being Legacy now.
Upgrading to V2 will be a seamless and transparent process as V2 has been publicly battle tested for over a year now.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved brody • about 1 year ago
