Error "The selected runtime is not supported in this region." switching to metal
When I try to switch any of the services in my project
cc6da1e6-256c-47fc-bf86-2d464d8eb369 (e.g. service 11f8563c-e639-4324-88d3-7ef47ddbad52 / deploy 681ad357-e19c-44e9-a1e4-88891dadad05)
to the Metal region they all fail with the error "The selected runtime is not supported in this region.", even though there is no option to change runtime visible in Settings for these services. I don't have any volumes.9 Replies
Project ID:
cc6da1e6-256c-47fc-bf86-2d464d8eb369,11f8563c-e639-4324-88d3-7ef47ddbad52,681ad357-e19c-44e9-a1e4-88891dadad05^only the first of those is a project ID, the other two are service and deployment IDs respectively
I found https://discord.com/channels/713503345364697088/1287814917638066227/1287923852122394727 which is the only instance of the same error in this server but it didn't seem too helpful
try doing
railway up again pleaseAh, retrying the deployment from the dash didnt work but
railway up did
I believe the other services are still affected though
e.g. e51c777b-426d-4c49-9f13-f2a2d1ba64d6 which is from a docker image, so cant railway up and 5a187175-54a0-407f-b518-490bc5e30c7b which is from githubI have switched the runtime for those services already, you can do a
ctrl / cmd + k -> deploy latest commit on those.Awesome, thank you!
Deploy latest commit was what I was missing, I was retrying the failed deployment
Its all resolved now, thanks again for the help!
redeploying a deployment would just redeploy it with the same runtime, it needed to be a fresh deploy.
i've brought this up with the team, this should be transparent to you, it shouldnt need someone from the team to intervene
Yeah makes sense on the difference, not sure why I thought a redeploy would work - and thanks for bringing it to the team
no problem!