Skip to content
Railway infra_error, CREATE_CONTAINER failures, restart rejected
eduardgannaban00
OP

a month ago

Hello Railway Support,

Our production application, STARK, is unavailable and returning HTTP 502.

We've investigated the issue and found that three consecutive deployments completed their image builds successfully but stalled at CREATE_CONTAINER, without startup logs or a recorded container error. Railway's deployment diagnosis identified an infra_error.

Affected resources:

  • Project: energetic-courtesy
  • Environment: production
  • Service: stark
  • Region: ams
  • Active deployment: f790dc15-1f4f-47c3-9a86-9d7ca144c8d1
  • Replica: 42e3f037-fbfc-49ee-892b-2aad38576d27

Failed deployments:

  • 4678ef51-2fe1-4f06-b610-9bdbe2f4f5d8
  • 4d2a17e2-57d9-4183-8dba-0b9f1cb3c631
  • 078bfe05-0fb8-474d-a295-9e35708a3469

The existing replica reports RUNNING, but Railway's HTTP proxy receives connection-refused errors on port 8080.

We attempted one restart of the existing successful deployment, but Railway rejected it with Problem processing request.

Restart trace ID: 505731890422795212

Our persistent volume, stark-volume, is attached at /app/data in ams, reports Ready, and contains approximately 410 MB of 500 MB.

Could you please investigate the Amsterdam container scheduler, deployment activation, stale replica state, and volume attachment coordination?

We need help restoring the service while preserving the existing persistent volume and its data. Please do not delete, replace, or reset the volume.

Production URL: https://stark-production-aeee.up.railway.app

Thank you.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

We've cleared the stale state left by the previous stark deployment, which was blocking your three new deployments and the restart. You can redeploy stark now.

This change didn't delete, replace, or reset stark-volume.


Status changed to Awaiting User Response brody • about 1 month ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...