2 months ago
Hello Railway Support Team,
I’m experiencing recurring stability issues with my deployment hosted on Railway.
The application runs normally for a few hours after deployment, but then the following issue occurs repeatedly throughout the day:
- The website loads only the UI (layout/template), but no data is fetched.
- It behaves as if there is a breakdown in communication between services.
- The issue can persist for several hours before resolving or after a redeploy.
What I have verified from my side:
- The application works perfectly on localhost with no issues.
- External services (e.g., Supabase) are running normally and responding correctly.
- There are no changes in the code between working and failing periods.
- Network requests appear to fail or not return data during the issue.
This leads me to suspect there might be:
- Intermittent internal networking issues between Railway services
- Container instability or service-to-service communication problems
- Possible resource throttling or cold start-related issues
Could you please investigate this behavior or guide me on:
- How to debug inter-service communication on Railway?
- Whether there are known issues related to deployments becoming unstable after some time?
- Any logs or metrics I should monitor to pinpoint the root cause?
This issue is affecting production reliability, so your support is highly appreciated.
Looking forward to your response.
Best regards,
2 Replies
2 months ago
Your project has a blue/green setup with Web, Admin, and Backend services, and you mention the UI loads but no data is fetched. If your frontend (Web Blue/Green) is a client-side app making requests from the browser to your backend, those requests cannot use the private network (railway.internal) since the browser is on the public internet, not inside Railway's network. You would need to ensure your frontend is calling the backend via its public domain. You can verify this by checking your browser's DevTools Network tab during the failure periods to see which requests are failing and what URLs they target. More details on client-side vs server-side requests are in our private networking docs.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
Railway
Your project has a blue/green setup with Web, Admin, and Backend services, and you mention the UI loads but no data is fetched. If your frontend (Web Blue/Green) is a client-side app making requests from the browser to your backend, those requests cannot use the private network (`railway.internal`) since the browser is on the public internet, not inside Railway's network. You would need to ensure your frontend is calling the backend via its public domain. You can verify this by checking your browser's DevTools Network tab during the failure periods to see which requests are failing and what URLs they target. More details on client-side vs server-side requests are in our [private networking docs](https://docs.railway.com/networking/private-networking/how-it-works).
2 months ago
I understand your point regarding private networking and client-side requests.
However, I’d like to clarify a few important details:
The frontend is using the public backend URL (not railway.internal).
The issue is intermittent:
The application works perfectly for a few hours.
Then suddenly, API requests stop returning data.
During failure periods, the UI loads correctly, but API calls either fail or hang.
This behavior suggests that:
The issue is not related to private networking misuse.
It might be related to service instability, routing, or container restarts.
To investigate further, I will check:
Network tab during failure periods (request URLs & status codes)
Backend logs during downtime
Meanwhile, could you please help clarify:
Are there any known issues with Blue/Green deployments causing intermittent routing problems?
Could backend services become temporarily unreachable from the public domain?
Are there logs or metrics for internal routing between services that I can access?
Status changed to Open Railway • about 2 months ago