Skip to content
Deployment fails
rishavpatel5
OP

12 days ago

All recent deployments of my backend service are failing. A GitHub-triggered deployment (332e8c35) failed at Build image after 36 seconds with no build logs. A CLI deployment using railway up (5c27e812, November 8, 23:59 IST) then failed with "Failed to snapshot repository. Please try again in a few minutes". An earlier deployment of the same service succeeded on November 8 with an identical Dockerfile and dependencies, and only application code has changed since. The Root Directory was changed from /backend to / during troubleshooting. Service: backend, region US West, project meticulous-caring. Can you check whether snapshots or builds are failing for this project?

Solved

1 Reply

Railway
BOT

12 days ago

Your GitHub-triggered deployment failed at the image build step at 18:24 UTC without producing any build output. GitHub is currently having an outage that causes build failures for projects that deploy from GitHub, and we're tracking it in GitHub Outage Affecting Builds.

That incident doesn't affect deployments made with the CLI, so it doesn't explain your railway up deployment. That one failed earlier in the process, at the code snapshot step at 18:30 UTC, with the "Failed to snapshot repository" error. Our records don't show why the snapshot failed.

You changed the Root Directory from /backend to / while troubleshooting, and that setting is still in place. Before you deploy again, set it back to the folder your Dockerfile was in when the November 8 deployment succeeded.


Status changed to Awaiting User Response Railway • 12 days ago


Railway
BOT

4 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 • 4 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...