Your container may not have a shell available. Railway's SSH feature requires either /bin/bash or /bin/sh to exist in your container, as it doesn't use traditional SSH but rather a WSS based connection that spawns a shell process.

That moderator answer is probably the right direction. status: SUCCESS / stopped: false only means the worker process is up; Railway SSH still needs a shell inside the image.

Since you’re using Bun, check whether the final image is minimal/distroless and missing /bin/sh:

command -v sh || command -v bash

If that returns nothing, add a shell to the runtime image, e.g. apk add --no-cache bash on Alpine, or switch to a base image that includes /bin/sh.

Also worth checking the worker logs for a simple startup heartbeat, just to confirm the Bun process is not forking and then leaving Railway with something odd. But for this specific railway ssh error, shell availability is the first thing I’d fix.