Hey there! We've found the following might help you get unblocked faster:

• 🧵 ❗Service stops scraping after a while - no crash, no logs - Hobby Plan

• 🧵 Unable to handle SIGINT

• 🧵 Container SIGTERM after 60-65 seconds despite healthy keepalive and health checks

• 📚 Deployments

If you find the answer from one of these, please let us know by solving the thread!

I re-created the container and after a while I still had this issue again. Everything seems correct, but Railway keeps stopping the container.

what is your start command ?

Current: BLANK (using Dockerfile CMD)

Dockerfile: backend/Dockerfile

Actual command: dumb-init -- node index.js

I redeployed the container again, and it has already sent one SIGTERM received, shutting down gracefully... on a healthy container

Thanks. I hope index.jshas an HTTP server that stays listening?

Yes, index.js absolutely has a persistent HTTP server that stays listening. Current deployment is the longest survival yet (92+ min). We're monitoring to see if it remains stable or if Railway sends another premature SIGTERM. The earlier crashes (after 5 sec, 29 sec, 9 min) were caused by Railway sending SIGTERM prematurely despite the server being healthy and passing all health checks.