24 days ago
Hi,
I’m following up on my previous ticket, which hasn’t received a response yet.
Since the infrastructure issue last week, I’ve noticed that your system is automatically and randomly enabling the Metal environment on some of my services. Unfortunately, when this option is enabled, my deployments consistently fail.
Could you please investigate and resolve this issue, and ideally prevent the Metal environment from being auto-enabled without manual action?
This is currently impacting the stability of my deployments, so a quick resolution would be greatly appreciated.
Thanks in advance for your help.
Best regards,
William
5 Replies
24 days ago
We are currently migrating Pro users' workloads to Railway Metal as part of our planned infrastructure migration, which started for Pro users on May 2nd. We can see that 8 of your 14 services are currently in a FAILED state. If Metal is causing your deployments to fail, you can roll back each affected service by going to Settings > Deploy > Regions and selecting a region without the "Metal (New)" tag, which will redeploy on the previous infrastructure. If the failures persist even after rolling back, please share the specific error messages or build logs so we can investigate further.
Status changed to Awaiting User Response Railway • 24 days ago
23 days ago
Hello, you dn't understand, i think is because i'm speaking english so bad 🙂
Look my account, each time i turned off Metal, 20 minutes after that it's turn on again alone, i receive hundred mail per day due to failed, can you solve this issue please 🙂 i don't want Metal for all my services, but unfortunately, your systeme re-enabled automatically all time
Status changed to Awaiting Railway Response Railway • 23 days ago
21 days ago
hello, now the metal button disapear but now each services as a new big issue that now i can't deploy nothing since today, can you help me asap because all my infrastructure cannot deploy nothing now
Thank you for your help
21 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 21 days ago
agazzi
hello, now the metal button disapear but now each services as a new big issue that now i can't deploy nothing since today, can you help me asap because all my infrastructure cannot deploy nothing now Thank you for your help
21 days ago
Hey,
We migrated everyone to metal builders. The issue you are facing is related to the versions of railpack/node/yarn that are used:
```
php │ 8.5.5 │ composer.json > require > php (>=8.3)
node │ 22.22.2 │ railpack default (22)
yarn │ 1.22.22 │ railpack default (1)
```
So yarn 1.22.22 is used, but your lockfile has most likely another version pinned. You either can change version in the lockfile or pin required version via railpack - https://railpack.com/languages/node#versions
UPD: hm, as I see successful builds were also using yarn 1.22.22. But in any case error is related to versions miss-match: e.g. error Your lockfile needs to be updated, but yarn was run with --frozen-lockfile
21 days ago
okay, let me check/update thx you for your help
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago