20 days ago
Hi Railway Support,
My production service is still routing to an old deployment despite multiple restarts and redeploys.
Public URL:
https://home-service-infrastructure-production.up.railway.app/api/version
Issue:
All requests are hitting old deployment:
"deploy_id":"db7ad7ed",
"production_mode":false
Expected:
"deploy_id":"b57cbc9d",
"production_mode":true
Evidence (5 repeated requests):
All responses consistently return db7ad7ed with production_mode:false.
Important context:
- New deployment
b57cbc9dis confirmed running correctly withPRODUCTION_MODE=true(verified via logs) - Restart was performed but traffic did not switch
- Only 1 replica is configured, yet routing appears stuck to old instance
Impact (critical):
Production is exposing unsafe/demo behavior:
- Demo login endpoints return valid tokens
- OTP debug codes visible in responses
- Potential unauthorized access risk
What I need:
- Force terminate old deployment
db7ad7ed - Ensure traffic routes to latest deployment
b57cbc9d - Verify domain routing is not stuck on stale replica
This is blocking production launch.
Thank you.
1 Replies
20 days ago
Your service's latest deployment currently has a FAILED status, which means traffic continues to route to the last successfully active deployment. You can verify this in the deployments view for your service in the project "grateful-consideration". To resolve this, try triggering a fresh redeploy from the deployment menu, and if the issue persists, check the build and deploy logs for errors that may be causing the failure.
Status changed to Awaiting User Response Railway • 20 days ago
13 days 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 • 13 days ago