2 months ago
Our Postgres services unreachable over public networking: the dashboard's Database Connection panel hangs at "Attempting to connect", and TCP-proxy connections (both the original proxy and a freshly created one) accept TCP and then immediately close — server closed the connection unexpectedly from psql, regardless of sslmode. Private networking is unaffected: our app connects and queries normally via postgres.railway.internal. Redeploying the database service did not help. This began today; the proxy worked two days ago. Possibly related: this volume was region-migrated from sfo to us-east4-eqdc4a on Aug 11.
Pinned Solution
2 months ago
Try to redeploy source image instead of a normal redeploy. You can do it by selecting your Postgres service, press CTRL+K, then select redeploy source image. This usually fixes the stuck state of "Attempting to connect" in the dashboard, and it might also fix the public network connection.
3 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Are there any error on the Deploy Logs of the Postgres service? Try Redeploy Source Image from the Command Palette
mayori
Are there any error on the Deploy Logs of the Postgres service? Try Redeploy Source Image from the Command Palette
2 months ago
No logs saved
2 months ago
Try to redeploy source image instead of a normal redeploy. You can do it by selecting your Postgres service, press CTRL+K, then select redeploy source image. This usually fixes the stuck state of "Attempting to connect" in the dashboard, and it might also fix the public network connection.
Status changed to Solved 0x5b62656e5d • about 2 months ago