a year ago
For the last 2 days I have been repeatedly trying to deploy an update to my server. The image builds, then gets stuck at the "Deploy > Create container" step. I've tried pushing various branches, including the same one that last successfully deployed.
The deployment process times out after about 30 minutes in one of 2 error states: "We were unable to connect to the registry for this image. If this error persists, please reach out to the Railway team." or "Failed to create deployment. If this error persists, please reach out to the Railway team"
The "Deploy logs" section is empty, so I am unable to debug this. Please could you give me some pointers here; I have been unable to update my live server for a couple of days.
ⓘ Deployment information is only viewable by project members and Railway employees.
4 Replies
a year ago
If I commit one file back at a time it seems to be at least deploying now for the first couple of files. Either it fixed itself or I'll be able to narrow down what caused it. It would be great to get some more debugging for problems like this, though!
a year ago
I have 2 identical branches: when I deploy from one, it works. When I deploy from the other, I get these errors. In this case, I can't see how this is a problem with my code.
a year ago
Looks like I fixed this issue by nuking my old main, then force pushing a working identical branch to main. I can't see how this is a code problem - maybe the deploy infrastructure had something bad in its cache?
Status changed to Solved brody • over 1 year ago