a year ago
Hi, we recently started receiving the error "Failed to upload code with status code 504 Gateway Timeout" when running "railway up", both from our CI and from local machines. Nothing about our setup has changed, and we have tried to deploy to multiple environments. Retried more than 20 times.
Here's an example deployment ID:
e463fa6f-e68b-41ad-ba66-f78fe83d9c0f
Our repository is not overly heavy, weighing in at about 15mb, which should be well possible to upload within the 15 second timeout. Besides, nothing about our setup or repository metrics have changed since we last deployed 2 days ago.
This seems to be an issue on Railway's end, but nothing in the Railway status dashboard indicates there should be an issue with the code uploads.
Untimely as always, we urgently require to deploy a new version of our backend, so urgency would be appreciated.
3 Replies
a year ago
Hi Louie,
We're looking into this issue now. It looks like you had a successful deployment 20 minutes ago. Can you confirm you didn't change anything on your end?
Regards, Christian
Status changed to Awaiting User Response railway[bot] • 11 months ago
a year ago
Hi Louie,
We're looking into this issue now. It looks like you had a successful deployment 20 minutes ago. Can you confirm you didn't change anything on your end?
Regards, Christian
We're on EU time, hence the late reply. But yeah, we didn't change anything, I was simply retrying for about an hour and all of a sudden it passed. So all seems good now, but of course we wouldn't like to see this happen in the future.
Status changed to Awaiting Railway Response railway[bot] • 11 months ago
a year ago
Thank you for letting me know. We're working on measures to prevent similar issues from happening in the future. I apologize for the inconvenience.
Status changed to Awaiting User Response railway[bot] • 11 months ago