17 days ago
Deploy is failing after stalling for 20 minutes,
start command:
uvicorn main:app --host 0.0.0.0 --port ${PORT:-8080}
Using railway metal for build.
only error logs are in build
image push
756.8 MB / 756.8 MB21.1s
=========================
Container failed to start
=========================
Failed to create deployment.
Nothing in deployment logs
35 Replies
16 days ago
Hey there,
First off, sorry for the poor experience. We did trace it to a situation to a host that the low forwarding was impacted. This is now resolved, if you can trigger another build, we can go ahead and debug that with you.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Seeing a similar issue, deploy fails, now deployment logs only build logs indicating failed health checks
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
I was having this same issue, removed metal for build, and today I was able to successfully deploy my app again. It does take a lot longer to deploy, but it works. Edit: I tried deploying again after some code changes and now I'm having this same issue again.
angelo-railway
Hey there, First off, sorry for the poor experience. We did trace it to a situation to a host that the low forwarding was impacted. This is now resolved, if you can trigger another build, we can go ahead and debug that with you.
16 days ago
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Hey there!
There was something with manual config that I just sorted on our end. Can you try redeploying and let me know if it works!
16 days ago
Running into a similar issue with one of my services: 1750d5ee-4c99-487f-b5cc-49c53b0bf73d
Status changed to Awaiting Railway Response Railway • 16 days ago
billdybas
Running into a similar issue with one of my services: 1750d5ee-4c99-487f-b5cc-49c53b0bf73d
16 days ago
Can you provide a link to it? Would be great!
Status changed to Awaiting User Response Railway • 16 days ago
noahd
Can you provide a link to it? Would be great!
16 days ago
Status changed to Awaiting Railway Response Railway • 16 days ago
billdybas
https://railway.com/project/7d34e953-a549-4983-9cf8-7511c221d576/service/1750d5ee-4c99-487f-b5cc-49c53b0bf73d
16 days ago
Can you abort any ongoing deploy and trigger a new redeploy?
Status changed to Awaiting User Response Railway • 16 days ago
noahd
Can you provide a link to it? Would be great!
16 days ago
I'm also running into this same issue, https://railway.com/project/9e3ad4a0-7f43-44ec-a7a8-b472372d3f66?environmentId=96763c06-a66a-4882-a581-e7e679c440cd
Status changed to Awaiting Railway Response Railway • 16 days ago
noahd
Can you abort any ongoing deploy and trigger a new redeploy?
16 days ago
Done. I tried redeploying twice but they both time out failing on the create container step.
16 days ago
15 days ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
15 days ago
We've been addressing infrastructure issues affecting deployments today, and fixes have been applied on our end. Long story short, we expanded capacity and added additional hosts. The build timeouts that you all saw were connected to the inability to find a machine within this time frame. Our monitoring is showing that we are holding up well in the meantime, however, we will continue to monitor this thread if there are issues.
Status changed to Awaiting User Response Railway • 15 days ago
6 days ago
Status changed to Awaiting Railway Response Railway • 6 days ago
6 days ago
6 days ago
Same issue here.
6 days ago
Same issue here :(
6 days ago
Same issue. Why no issue elevated in Railway Status page?
6 days ago
+1 some issue
6 days ago
+1 same issue
6 days ago
Same here
6 days ago
Same issue!
6 days ago
same here :(
6 days ago
amnesia
same...
6 days ago
Managed to successfully deploy, finally
6 days ago
Howdy!
Was a bug with a part of the deploy flow. Should be good now! Can you try again?
Status changed to Awaiting User Response Railway • 6 days ago
6 days ago
🛠️ The ticket Container startup failures on some deployments has been marked as triage.
6 days ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
