7 days ago
Hi Railway team,
Our production gateway service is stuck at one replica in the legacy sfo region. The intended multiRegionConfig is one replica each in us-west2, europe-west4-drams3a (Amsterdam), and asia-southeast1-eqsg3a (Singapore).
We set those regions in our Railway IaC config (.railway/railway.ts, partial nyrathen-world-gateway) and the GitHub config apply reported success. We also tried adding Amsterdam and Singapore in the dashboard; the patch showed as STAGED and was accepted, but no new deployment/config appeared. Deploying from the dashboard reset the region list to sfo. Live config still reports multiRegionConfig: { sfo: { numReplicas: 1 } }.
Could you check whether this service has a stale/invalid dashboard-side region value that needs clearing, and confirm the correct way to migrate it to the three supported region identifiers? If sfo is invalid for this service, please clear the stale value so we can apply the valid config. We are on Pro.
Project: Nyrathen
Environment: production (38f196e1-6d0a-430b-a539-9e2ccb616a9e)
Service: nyrathen-world-gateway (258cd6c7-0554-40e4-aece-26b00e7cf3eb)
We only want to change the gateway. The game/state services and shared world should remain as they are. Thank you.
2 Replies
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
Update, 29 Sep 2026: The latest service-config read still shows sfo:1 only; the gateway is online with one replica. The existing Railway support-AI thread confirms that the environment apply was refused with “An unknown error occurred”, including the isolation test adding only us-west2 while retaining sfo. A normal deploy does not commit the staged region changes.
Railway's AI says this requires a Railway team member. I tried opening the private technical support thread it recommended, but the site blocked the duplicate and directed me back to this open thread. Please route this case to a Railway engineer and identify the server-side reason the environment apply is refused. We still want to change only the gateway and preserve the shared world.
6 days ago
Sorry for the trouble this caused. Your region config was fine, and the refused applies weren't caused by it.
We've moved nyrathen-world-gateway to one replica each in us-west2, europe-west4-drams3a and asia-southeast1-eqsg3a, and the sfo replica has been removed. Nothing else in the project was changed.
If a later change on production gets refused the same way, let us know here.
Status changed to Awaiting User Response Railway • 6 days ago