Issue Summary

Deployment fails immediately after successful build with no deployment logs. The app works perfectly locally but crashes on Railway before any code executes.

Environment

• Service Type: Web service (Node.js)

• Build System: Nixpacks v1.38.0

• Node Version: nodejs_22 (detected by Nixpacks)

• Region: us-west1

What's Happening

1. Build completes successfully ("Successfully Built!")

2. Deployment fails immediately

3. No deployment logs appear at all - the Deploy Logs tab is completely empty

4. Email notification says "Build failed!" despite build logs showing success

5. Previous deployment (older commit) is still running fine

What I've Tried

• Removed healthcheck configuration - still fails

• Removed volume mount [[mounts]] from railway.toml - still fails

• Added extensive console.log statements at the very first line of the app - none appear in logs

• Verified no syntax errors (node --check passes on all files)

• Verified npm ci installs successfully with 0 vulnerabilities

• Verified app starts and runs correctly on local machine

• Simplified railway.toml to minimal configuration

Current railway.toml

toml

[build]
builder = "nixpacks"

[deploy]
startCommand = "node src/server.js"
healthcheckPath = "/health"
healthcheckTimeout = 60
restartPolicyType = "on_failure"
restartPolicyMaxRetries = 3

Current Environment Variables

• DATABASE_PATH=/app/data/replies.db

• CONFIG_PATH=/app/data/workspaces.json

• PORT (set by Railway)

Volume Configuration

• One volume named "data" mounted at /app/data (configured in dashboard)

Build Log (shows success)

╔════════ Nixpacks v1.38.0 ═══════╗
║ setup      │ nodejs_22, npm-9_x ║
║ install    │ npm ci             ║
║ start      │ node src/server.js ║
╚═════════════════════════════════╝
...
=== Successfully Built! ===
Build time: ~26 seconds

Key Observations

• The container appears to crash before Node.js even executes (no console.log output)

• An older deployment of the same service is still running successfully

• The issue started when trying to deploy a new commit

• Local testing shows the app starts within 2-3 seconds and responds to health checks

Request

Please investigate why the container fails to start after a successful build. Since there are no logs at all, we cannot determine the cause on our end.

Service URL:instantly-unibox-production.up.railway.app

Thank you for your help.