Railway ignoring Node 20 configuration (Nixpacks using Node 18) → causing repeated 502 failures
debearr
HOBBYOP

16 days ago

Greetings,

I am exhausted and frustrated because I have been dealing with the same problem for weeks.

Railway ignoring Node 20 configuration (Nixpacks using Node 18) → causing repeated 502 failures

Message (copy this):

Hi team  I need help with a deployment issue that has been blocking my production service for days, despite following all the official docs.

**Project:** synqra-production / service: synqra-os  
**Domain:** https://synqra.co

---

## ISSUE SUMMARY

No matter what configuration I apply, Railway continues to build with **Node 18**, even though my project requires **Node 20** and explicitly sets it.

As a result, the app deploys but immediately fails with:

**Application failed to respond  502 error**

There are **no runtime logs**, only the splash error page.

---

## WHAT I HAVE ALREADY TRIED (multiple times)

### ✔ 1. Added NIXPACKS_NODE_VERSION=20  
In the service  Variables panel:

NIXPACKS_NODE_VERSION=20


Verified saved. Redeployed.  
**Still building with Node 18**.

---

### ✔ 2. Created root-level nixpacks.toml  
File at repo root:

[build]
nodejsVersion = "20"
[start]
cmd = "npm run start"


GitHub shows the file is committed and synced.  
Redeployed again.  
**Still building with Node 18**.

---

### ✔ 3. Updated root package.json engines

"engines": {
"node": "20.x",
"npm": ">=10.0.0"
}


Redeployed.  
**Still building with Node 18**.

---

### ✔ 4. Updated app package.json start script  
Inside `apps/synqra-mvp/package.json`:

"start": "next start -p ${PORT:-8080} --hostname 0.0.0.0"


Build still forces Node 18.

---

### ✔ 5. Deleted overrides  
Deleted:
- railway.json  
- .nvmrc  
- .node-version  

Pushed. Redeployed.  
**Still forces Node 18**.

---

## THE CORE PROBLEM

Every single build log starts with:

Using Nixpacks
pkgs: nodejs_18, pnpm_9_x


This means the Nixpacks override is not being honored.

I need Railway to either:

1. Tell me exactly how to force Node 20 reliably, OR  
2. Confirm if there is a caching or version pin issue on Railway’s side, OR  
3. Point me to the correct file or setting that overrides Nixpacks.

---

## EXPECTED OUTCOME

- A clean build with Node 20
- No more 502 failures
- The app actually starts and responds

At the moment, I can’t get past the incorrect Node version.

---

## EXTRA INFO

- Monorepo structure  
- Next.js app located at: `apps/synqra-mvp`  
- Root workspace orchestrates build/start scripts  
- Railway project URL:
  https://railway.app/project/640aa279-0093-43b6-8269-ad264bc657eb

---

I would greatly appreciate direct guidance or confirmation of what’s overriding Node 20 so I can finally get the production service running again.

Thank you!

Leroy 

Email: tomford46661@gmail.com

Ph: 647 961 5032

$10 Bounty

1 Replies

Railway
BOT

16 days ago

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

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


Loading...