Deployment taking forever
nick12
HOBBYOP

2 years ago

Hi, I have been uploading my Django site today and it's been taking around 15-20 minutes to deploy. It seems to be hanging for about ten minutes between Celery deploying and the server deploying. Sometimes causing about ten minutes of downtime.

Is there an on-going issue with Railway today?

Thanks

18 Replies

nick12
HOBBYOP

2 years ago

N/A


2 years ago

no known issues, try removing and redeploying


nick12
HOBBYOP

2 years ago

Removing what?


2 years ago

the deploy


nick12
HOBBYOP

2 years ago

I've been doing that all day


2 years ago

okay then please provide a link to the service


nick12
HOBBYOP

2 years ago

I don't know where to find the service ID


nick12
HOBBYOP

2 years ago

I found the project ID:


nick12
HOBBYOP

2 years ago

6d42db87-7a88-4e8b-85fe-1365cf208831


2 years ago

please provide a link to the service


nick12
HOBBYOP

2 years ago

the website?


2 years ago

to the railway service


nick12
HOBBYOP

2 years ago

this? jobsite.up.railway.app


nick12
HOBBYOP

2 years ago

Hi, still having this issue today. Any update?


jhud
PRO

2 years ago

I'm also having this problem after trying canceling, re-pushing, and re-deploying all day. I see some incidents on the Railway status page. https://status.railway.app


jhud
PRO

2 years ago

I only made minor code changes to my repo unrelated to resources or deploy, but today all my deploy attempts are timing out, getting stuck on the "Deploy > creating containers..." step forever. The "Deploy logs" section is empty, so I am unable to debug this.

This is stopping me from pushing updates to production. Is this a general problem? How can I debug this? Thank you!


2 years ago

looks like deploys are going out fine

1288921513377927279


jhud
PRO

2 years ago

Now the error message is different when re-deploying the same release. "We were unable to connect to the registry for this image. If this error persists, please reach out to the Railway team."

Attachments


Welcome!

Sign in to your Railway account to join the conversation.

Loading...