I have a Next.js 16 app deployed on Railway that shows "Application failed to respond" every time someone tries to access it, even though the deployment itself shows as successful.

The app runs perfectly on my local machine. The Railway runtime logs show almost nothing useful, only a single npm warning about --omit=dev, no actual error messages. I have verified that all environment variables are set correctly in Railway, including my Supabase URL, Stripe keys, and Resend API key.

I have tried redeploying multiple times, restarting the service, cleaning up all variables in the Raw Editor, and fixing a module-level initialization issue in the codebase. None of these resolved the problem.

The Request ID from the failed response is: sfo1COtITmWxcRvV2prcFg

I need help seeing the actual startup error that Railway is not surfacing in the runtime logs, since something is clearly crashing before the app can bind to its port and respond.