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

• 🧵 Container builds successfully but produces zero deploy logs
• 🧵 Only a single TCP proxy is allowed per service instance
• 🧵 help building my application

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

I had the same problem but with bun, and the fix for me was prefixing the build and start scripts in my package.json (which I specify as cmds in railway.toml) with bun --bun , now it looks like this

    "build": "bun --bun next build --turbopack",
    "start": "bun --bun next start",

It seems to be a problem with node because with Railpack 0.11 I was seeing bun as the runtime in my deployment, while with 0.12 I see both bun and node. After the fix I had it still shows both of them but it just deploys and works fine.

Hi! Do you have a Dockerfile for this?

I don't use Dockerfile, I use Railpack directly.

I tried to see if this was possible with node but --node is an invalid option.

I'm not sure what fixed it, but I updated one of my packages today and the deployment was successful without crashing.