3 months ago
Hey, I switched to railpack a week ago, and its been working fine. However, I have some really weird issues with my Nextjs. I pushed 2 commits yesterday - both just adds an article markdown file, and thats it. No compilation errors, everything builds fine. The first commit was built and deployed fine on railway, while the other just started deploying, then shut down the container and stopped.
```
You reached the start of the range
Dec 13, 2025, 7:40 PM
Starting Container
npm warn config production Use --omit=dev instead.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"
39 migrations found in prisma/migrations
No pending migrations to apply.
Stopping Container
You reached the end of the range
Dec 13, 2025, 7:41 PM
```
Why does this happen? There is literally no code change, only a markdown file change? No error logs, everything works locally, I don't understand.
This is how it looks when it works:
```
You reached the start of the range
Dec 14, 2025, 7:21 AM
Starting Container
npm warn config production Use --omit=dev instead.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"
39 migrations found in prisma/migrations
No pending migrations to apply.
Stopping Container
Starting Container
npm warn config production Use --omit=dev instead.
> graidable@0.1.0 start
> next start -p 3001
▲ Next.js 15.5.9
- Local: http://localhost:3001
- Network: http://10.250.16.48:3001
✓ Starting...
✓ Ready in 578ms
```
BTW, the project selector in the railway help is broken, it goes off screen and I cant scroll downwards to select the correct project.
2 Replies
3 months ago
hey @lukasthrane
thats super weird usually if it builds fine locally it should be ok. seeing the logs it looks like it finishes the prisma stuff and then the process just exits
check if you accidentally changed the service type to a Job or something that is meant to exit? cause "Stopping Container" usually means the main process exited with code 0 which happens if railway thinks the task is done
if its definitely a Service try checking your Metrics tab. sometimes if nextjs runs out of memory during boot it just dies silently without printing the error log. if ram is hitting the limit try bumping it up
also double check your start command in the service settings. maybe force it to be explicit instead of auto detected
npm run start
or whatever your script is just to be safe
re the ui bug yeah that happens lol. try zooming out in your browser cmd - or ctrl - usually lets you reach the bottom buttons
hope that helps let us know if you find more logs
anarchistmanifesto
hey @lukasthranethats super weird usually if it builds fine locally it should be ok. seeing the logs it looks like it finishes the prisma stuff and then the process just exitscheck if you accidentally changed the service type to a Job or something that is meant to exit? cause "Stopping Container" usually means the main process exited with code 0 which happens if railway thinks the task is doneif its definitely a Service try checking your Metrics tab. sometimes if nextjs runs out of memory during boot it just dies silently without printing the error log. if ram is hitting the limit try bumping it upalso double check your start command in the service settings. maybe force it to be explicit instead of auto detectednpm run startor whatever your script is just to be safere the ui bug yeah that happens lol. try zooming out in your browser cmd - or ctrl - usually lets you reach the bottom buttonshope that helps let us know if you find more logs
3 months ago
It works fine sometimes, I made no changes to the service before it randomly started exiting for no reason. I have allocated more than enough memory, the metrics always shows way less usage than the cap. It always stops and starts again, only working 20% of the time for no apparent reason. I don't know what you mean by changing the service type to a "Job", as I haven't touched any of the config in a while. I tried transferring to railpack from nixpacks since I thought this might solve it, but that didn't change anything. The start command is also set, and has no effect.