10 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.
1 Replies
10 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.