Hey there! We've found the following might help you get unblocked faster:

• 🧵 FAILED DEPLOYMENT

• 🧵 Deployment failed. Failed to build an image

• 🧵 Deployment failed

• 🧵 Failed to create deployment

If you find the answer from one of these, please let us know by solving the thread!

Hmmm we don't really have any reported issues about that.
Could I get a bit more info on the issue?

Hi Noah,

Thanks for looking into this. Here's a detailed breakdown:

Problem

Since January 8th, every deployment fails at "Creating containers" with absolutely no deploy logs appearing. The build completes successfully, but the container never starts.

Exact Behavior

Build phase: Completes successfully (all Docker stages finish, image push succeeds)

Deploy gets stuck at: Deploy › Creating containers...

Deploy Logs tab shows: "No logs in this time range"

After 5-10 minutes: Deployment marked as FAILED

100% reproduction rate - happens on every single deployment

What We've Already Tried

We've systematically gone through every Railway v2 troubleshooting step:

Infrastructure changes:

Switched from node:20-alpine to node:20-slim (Debian) due to Alpine networking issues

Added IPv6 binding: app.listen(port, '::')

Tried ENABLE_ALPINE_PRIVATE_NETWORKING=true variable

Increased healthcheck timeout: 30s → 180s

Disabled healthcheck completely to test

Added CORS allowlist for healthcheck.railway.app

Debugging attempts:

Added extensive logging to entrypoint script (first line: echo "Container starting...")

Changed from sh to bash entrypoint

Added DATABASE_URL validation before startup

Result: None of these changes made any difference. The entrypoint script never executes (not even the first echo appears in logs).

Latest Build Logs (Successful)

[inf] exporting to docker image format

[inf] containerimage.digest: sha256:af8dd2a8c43f944049a9624d8df43c529907800ae4e3dbc066e3b43b7986d3a4

[inf] image push

Build completes every time

Deploy Logs (Always Empty)

No logs in this time range

Container never starts, so logs never appear

Current Config

Dockerfile:

FROM node:20-slim AS builder

# ... build stages ...

FROM node:20-slim

CMD ["bash", "/app/scripts/docker-entrypoint.bash"]

railway.toml:

[deploy]

# healthcheck disabled for testing

restartPolicyType = "ON_FAILURE"

restartPolicyMaxRetries = 3

Tech Stack

NestJS on Node 20

pnpm package manager

Prisma ORM with PostgreSQL (Railway Postgres)

Migrations run in Docker entrypoint script

Key Observation

The app was working fine until January 8th. We made zero backend code changes - this started happening spontaneously. The container is built successfully but Railway never executes it.

What Would Help

Any internal logs from Railway's container orchestration layer?

Why is the container not being started after successful build?

Could this be related to builder region, registry issues, or v2 runtime changes?

We've tried everything in the docs and Help Station threads. At this point we need Railway's internal visibility to understand what's blocking container startup.

Thanks for your help.

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!

🛠️ The ticket Unable to deploy has been marked as in progress.

Hey there! We resolved this on our end and it shouldn't happen again going forward. Can you try and see if you're still running into this? Appreciate it!

Hello,

I'm currently unable to deploy my project because I can no longer connect my GitHub account.

When I try to authenticate, I get the following error:

"Error authenticating with GitHub – Problem completing OAuth login"

Because of this, the GitHub connection fails and the deployment is blocked.

Could you please help me resolve this issue or let me know if there’s something I need to reset or reauthorize on my side?

Thanks in advance for your help.

Best regards,

✅ The ticket Unable to deploy has been marked as completed.