3 months ago
I have two separate Railway projects that communicate via public URL. Several times a day, one service loses the ability to reach the other, and both of my apps go down. The only way I can get them up again is to manually redeploy.
My understanding is that private networking requires both of my apps to be inside the same project. I wish I'd know that, but I’m a vibe coding rookie. Consolidating them now (each has a database) is going to be a nightmare.
Is this an inevitable reliability issue with cross-project public URL calls between Railway services?
Is there anything I can do on the configuration side, or is the only solution merging these two into one project?
1 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
Private networking is scoped to a single project and environment, so cross-project calls must go over public URLs, which is correct. Your logs show repeated read timeouts hitting the other project's public domain. Consolidating both services and their databases into one project so they can communicate over railway.internal addresses would eliminate the public internet hops and is the recommended path. You can add multiple databases to the same project with no issue. The private networking docs cover the setup once everything is in one project.
Also note that using the public endpoint across services will result in egress charges whereas internal networking will not.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago