Persistent npm install failure due to 504 Gateway Timeouts on builde
escorpium
PROOP

9 months ago

Hello,

My deployment is persistently failing/hanging at the npm install step for my Node.js project.

I have already performed extensive debugging and can confirm the issue is not with my application code but with the builder's network connectivity to the npm registry.

Debugging steps already taken:

  1. Verified the package.json file is correct and complete.

  2. Ensured NODE_ENV=production is set.

  3. Disabled source code cache via railway.toml (nixpacks.source_cache = false).

  4. Forced the use of the official npm registry and verbose logging by adding an .npmrc file.

The verbose logs from the latest build clearly show multiple 504 Gateway Timeout errors when trying to fetch packages from registry.npmjs.org.

Could you please investigate the network health of the builders assigned to my project and consider purging any and all build-related caches on your end?

Project ID:

Solved

1 Replies

sarahkb125
EMPLOYEE

9 months ago

Hey there wave emoji

GCP is currently undergoing an incident. We're seeing GCP build degradation on our side. We've status'd to indicate. You can always see our status for incidents here: https://status.railway.com/

We're also seeing incidents light up across the internet at other providers who similarly have a dependency on GCP for certain services. Please send some hugs for your fellow on-call engineers today.

Status changed to Awaiting User Response Railway • 9 months ago

Status changed to Solved sarahkb125 • 9 months ago

Loading...