2 years ago
Hi, I recently upgraded to a Pro plan and increased the size of a Postgres service in my project. After Postgres redeploy, connections in my other services to Postgres started timing out. Connections over the public URL work fine, but not via the internal network.
Is this a known bug? What can I do to diagnose and resolve this?
1 Replies
2 years ago
Hello,
This is likely due to being on the Legacy runtime, see our docs page for more details - https://docs.railway.app/guides/private-networking#initialization-time
The good news, is that we now have the V2 runtime that completely solves the private networking initiation bug you are running into.
You can change your services over to the V2 runtime in their service settings.
The new runtime has been out for a while now and at this point it is fully backwards compatible!
Status changed to Awaiting User Response Railway • over 1 year ago
Status changed to Solved echohack • 10 months ago