It looks like rolling back to the commit before railway metal fixed it, how do I disable railway metal.

Hello,

Railway Metal wouldn't be the culprit here, is has no effect on the application itself.

This is likely due to the builder you are using, in the service settings, try switching to Railpack.

Best,
Brody

Hey Brody,

Thanks for getting back to me!

Are you sure it’s not Metal causing the issue? When I use Metal, it doesn’t work, but when I don’t, it does. Could my builder have switched over when the automatic Metal deployment happened?

I’m currently travelling, so I can’t do a thorough investigation right now, but I’ll leave Metal off for now to keep my apps running smoothly.

Let me know what you think!

Cheers,

Ollie

Hey Ollie!

That sounds alright to me. As Brody mentioned though, metal shouldn't affect the app itself so yes when you are at desk, please check if there the configuration (esp regions) may have changed.

Hope you have safe and happy travels!

Hey Chandrika,

Thanks for getting back to me. I'm back from holiday now and really need to get this sorted out.

I’ve been doing some testing this morning — I noticed the region had switched from US-2 to US-1, so I changed it back, but unfortunately that didn’t solve the issue.

Essentially, I have to roll back to the deployment just before the automated Metal deployment. Any newer deployments don’t work — which is a serious problem, as I can’t make any updates to my app. The issues all seem to have started with the automated Metal deployment, and there were no changes made on my end at that time.

Do you have any ideas on what might have changed during that Metal deployment that could be causing this?

Also, the deploy logs from the newer (non-working) deployments look quite odd.

Here’s a log from a recent failed deployment:

And here’s one from the working rollback (pre-Metal auto deployment):

As you can see, the deploy logs are behaving completely differently — the post-Metal update ones don’t seem to be reaching my code at all. As mentioned, I haven’t made any changes on my end, so this appears to be something that was altered during the automated Metal deployment/build. If it’s not Metal itself — since you mentioned it shouldn’t affect the app — is there anything else that might have been changed at the same time?

Thanks for your time.

Ollie

I've also tried switching to Railpack, no luck there either.

Do you have any dependencies that weren't pinned and was pulling the latest version?

When we perform a re-deploy, an exact copy of your code is re-deployed. If you have any external dependencies that isn't pinned to versions they were using, they will be re-installed from the latest version.

Unfortunately that's a app/code-specific issue and we can't help with troubleshooting the "why" behind it

Hey,

Thanks so much for your response

I can’t think of anything else on my end. I really don’t believe it’s related to my app, as I didn’t make any changes.

Before the Metal update and the automatic redeploy, everything was working smoothly—I could build and deploy without any issues.

Since the Metal update and auto-redeploy, I’ve been unable to build or deploy at all, and I’ve had to revert to the last working version just before the update.

I was actually on holiday at the time, so I wasn’t making any changes to the app.

Is there anything else you can think of that I should check—anything that might have changed as part of that automated redeploy or Metal update?

Really appreciate any help you can offer. Sorry it’s a tricky one! Frustratingly, if I can’t get it sorted, I may have to move away from Railway, as I’ve got some urgent updates that need pushing out.

Cheers,
Ollie

Hello,

Just letting you know that I've pushed this into our community bounties list since the Railway team can only provide support for issues related to the Railway platform or product.

Best,
Brody

Hey Brody,

Thanks for adding the bounty!

Just one more thing to double-check — my deployment outputs match the issues described in these two resolved threads:

• https://station.railway.com/questions/railway-issue-applications-stop-working-faaffebe

• https://station.railway.com/questions/admin-endpoint-disabled-0032e564

It looks like you resolved those by adjusting a setting on your end. Could it be the same issue in my case, or is it likely to be something different?

Appreciate your time and help with this!

Best regards,
Ollie

Hey Ollie,

I've reviewed those threads, and since the symptoms are similar, I went ahead and switched your Builder to Railpacks, which appears to have resolved your issue.

But I would like to clarify our current support approach. We do not offer direct team support for application-level or configuration issues and have transitioned to the community bounty system. This is why I added a bounty rather than troubleshooting the issue directly, as would have been done in those older threads.

While switching your Builder to Railpack resolved your issue this time, future support for application-level or configuration issues will be exclusively answered by the community.

Regards,
Brody

Hey Brody,

Thanks so much — it looks like we’ve got this one sorted!

I really appreciate you taking the extra time to dig a bit deeper, even though it’s outside the usual process. It’s great to have my deploys working again — I’ve got some much-needed updates to make and release now!

Best regards,
Ollie