App deploys successfully but returns 502 Bad Gateway

Question

The problem: \- App starts and runs (see logs below) \- Binds to correct port 8080 \- Railway's edge returns 502 with x-railway-fallback: true \- Request ID: Auq5DUFaQqCgfg9\_g4a9AQ Error: Application failed to respond This error appears to be caused by the application. If this is your project, check out your [deploy logs](https://docs.railway.com/guides/logs) to see what went wrong. Refer to our [docs on Fixing Common Errors](https://docs.railway.com/guides/fixing-common-errors) for help, or reach out over our [Help Station](https://station.railway.com). If you are a visitor, please contact the application owner or try again later. Request ID: GZH\_JtWRTfae6mGyg4a9AQ Repo: Logs: Starting Container npm warn config production Use `--omit=dev` instead. \> sc-mobile-backend@1.0.0 start \> node dist/app.js Swagger spec loaded successfully $$dotenv@17.0.1$$ injecting env (0) from .env – $$tip$$ encrypt with dotenvx: $$dotenv@17.0.1$$ injecting env (0) from .env – $$tip$$ encrypt with dotenvx: $$dotenv@17.0.1$$ injecting env (0) from .env – $$tip$$ encrypt with dotenvx: 🔧 PORT detection: { envPORT: '8080', finalPORT: 8080, source: 'Railway env' } 🔧 Initializing server... 📍 Environment: development 🌐 PORT: 8080 (Railway) 📁 File extension: JavaScript 🚀 Salsa Candela API running on port 8080 📋 Documentation: 🌐 Server bound to: 0.0.0.0:8080 Server startup complete - Ready for connections 💾 Memory usage: { rss: '85MB', heapTotal: '34MB', heapUsed: '22MB', external: '3MB' } 🔄 Process alive, uptime: 141 seconds 🔄 Process alive, uptime: 151 seconds npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c node dist/app.js npm error A complete log of this run can be found in: /root/.npm/\_logs/2025-08-13T21\_46\_51\_540Z-debug-0.log Stopping Container 🔄 Process alive, uptime: 10 seconds 🔄 Process alive, uptime: 20 seconds 🔄 Process alive, uptime: 30 seconds 🔄 Process alive, uptime: 40 seconds 🔄 Process alive, uptime: 50 seconds 🔄 Process alive, uptime: 60 seconds ...