3 months ago
Hi ! I have hosted my small website on railway server and it is my first time hosting anything so I am still new developer,
my question that I found that the service reach the limit and railway stopped it manually
you reached the start of the range
Jan 31, 2026, 3:36 PM
Stopping Container
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c node index.js
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-02-12T03_10_02_031Z-debug-0.log
these logs was in 27/02
I want to know why railway stopped the service?
if it reach the limit shouldn't railway send me an email, or let me save my data before delete it, I hade sql file inside the server,
for now I made a new service but I want to know how to avoid this in the future.
Best regards Crazy Salong
Pinned Solution
3 months ago
Hi, from the logs it doesn't look like your website or data was deleted, the container was just stopped. The SIGTERM in your logs means a termination signal was sent to the container, which usually happens when a service is stopped, redeployed, or when a project hits its usage/spending limit. Railway normally won't delete your project or database automatically in that case, it just stops the service. One important thing, the container filesystem is ephemeral, files stored inside the container (like things in /app) aren't guaranteed to persist if the service redeploys. Hopefully this clears things up a little?
6 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
You need to be the one to configure notifications. (Sorry, but to be blunt, this is the user's responsibility to track their own usage.)
Attachments
0x5b62656e5d
You need to be the one to configure notifications. (Sorry, but to be blunt, this is the user's responsibility to track their own usage.) 
3 months ago
Thank you for your help.
However, I still feel that my main question wasn’t fully answered. I’m trying to understand how to prevent this situation from happening again.
My main concern is: was my server/database deleted because the usage reached a certain limit? If that is the case, what should I do next time if my project reaches that limit?
For example, will the service stop, or will the data be deleted automatically? And what would be the recommended way to avoid losing the server or database in the future?
Thank you for your clarification.
0x5b62656e5d
You need to be the one to configure notifications. (Sorry, but to be blunt, this is the user's responsibility to track their own usage.) 
3 months ago
after checking the notification I relies that I hade the same sitting as in the photo you send but I still didn't get any thing in the email
3 months ago
Hi, from the logs it doesn't look like your website or data was deleted, the container was just stopped. The SIGTERM in your logs means a termination signal was sent to the container, which usually happens when a service is stopped, redeployed, or when a project hits its usage/spending limit. Railway normally won't delete your project or database automatically in that case, it just stops the service. One important thing, the container filesystem is ephemeral, files stored inside the container (like things in /app) aren't guaranteed to persist if the service redeploys. Hopefully this clears things up a little?
crazy-salong
Thank you for your help. However, I still feel that my main question wasn’t fully answered. I’m trying to understand how to prevent this situation from happening again. My main concern is: was my server/database deleted because the usage reached a certain limit? If that is the case, what should I do next time if my project reaches that limit? For example, will the service stop, or will the data be deleted automatically? And what would be the recommended way to avoid losing the server or database in the future? Thank you for your clarification.
3 months ago
You can't prevent the shutdown of a service when a usage limit is reached.
You can either raise the limit or upgrade to the Pro plan.
2 months ago
thank you very much for your help
Status changed to Solved nico • 2 months ago