18 days ago
Symptoms: App starts successfully (logs confirm Nest application successfully started on port 8080), cron jobs run, but public domain returns connection timeout. Zero incoming requests visible in logs.
Tried: Redeploy, restart, removed/re-added public domain, switched Metal/Legacy and back
Timing: Started working after merge to main ~00:26 UTC Feb 17, went unreachable shortly after
4 Replies
18 days ago
Your app is listening on port 8080 .. check Settings - > Networking and see what port is shown. If Railway is routing to a different port, that would explain the timeout with zero incoming requests in logs. Also are you using 0.0.0.0 as the host, not localhost or 127.0.0.1?
18 days ago
Thanks for the quick response. All those items are fine. In fact, seems intermittent. The service is mostly unreachable, and then it becomes available for short timeframes. So it feels more like a Railway infra issue than my code or config.
Thanks
hungry-lemon-daddy
Thanks for the quick response. All those items are fine. In fact, seems intermittent. The service is mostly unreachable, and then it becomes available for short timeframes. So it feels more like a Railway infra issue than my code or config.Thanks
18 days ago
oh ,Also do you have serverless enabled ? ..cause app sleeps after inactivity and takes time to wake up.
17 days ago
Thanks for the response. The api has now started working again. no code or config changes. This was an outage from railway. The stability of this platform does not seem great.
