Hi! I’m on a Railway trial account and I’m having trouble deploying a Node/Vite app using the local Railway CLI, not GitHub.

The deploy never reaches the build step. The CLI reaches:

Indexing...

Uploading...

then fails with:

operation timed out

In the dashboard, the deployment stays at:

Initialization > Snapshot code / Taking a snapshot of the code...

After 10 minutes it fails with:

Failed to create code snapshot. Please review your last commit, or try again.

Railway diagnosis says the deployment timed out at the SNAPSHOT_CODE stage, with no repo, branch, or source image present.

Things already tried:

• Re-logged into Railway CLI
• Updated Railway CLI from 4.58.0 to 4.59.0
• Cleared/removed the broken Source config from the service
• Tried deploying from the project root
• Tried deploying from a clean folder created from git archive HEAD
• Tried railway up . --path-as-root --service web --environment production --detach
• Added .railwayignore, although it looks like CLI deploy mainly respects .gitignore

Project size/context:

• Around 700 tracked files
• node_modules, backups, local DB, and dist are ignored
• Local npm run build passes
• Prisma schema validation passes

Is this a known issue with local CLI uploads getting stuck at SNAPSHOT_CODE? Is there a way to debug what the CLI is uploading, or should I try creating a fresh service and moving/reattaching the existing volume?