2 months ago
Im setting up a Node.js service in US East (my default regionin "Preferred Deployment Region"). When my config file railway.json is us-east4, I get an error on deploy: "User does not have access to region us-east4". But my database, a cronjob, and my other service are in the US East region.
Any ideas whats going on?
3 Replies
2 months ago
The region identifier for US East in config-as-code is us-east4-eqdc4a, not us-east4. Update your railway.json to use the full identifier and the deploy will work. The full list of region identifiers is in our Regions docs.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Oh! My mistake!
Just for your interest, when you put a wrong region in railway, you get an error: "Region us-east is not available. Available regions are: [europe-west4-drams3a, europe-west4, asia-southeast1, us-east4, us-west1, us-west2, asia-southeast1-eqsg3a, us-west2-aws, us-east4-eqdc4a]"
(I get the first "us-east4" region, I didnt see "us-east4-eqdc4a" at first)
Thanks you!
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved chandrika • 2 months ago
2 months ago
The region identifier for US East in config-as-code is us-east4-eqdc4a, not us-east4. Update your railway.json to use the full identifier and the deploy will work. The full list of region identifiers is in our Regions docs.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved oberddan • 2 months ago