43 minutes ago
Project: impartial-recreation (05926285-17d6-439f-839c-319fb4fe9bfd)
Service: zooyque-web — STAGING environment
(env b170a302-a9df-466a-953b-211d89bbc06f, service 63c31570-c4f1-4cec-9da1-d5366c741bd5)
Every deployment in this environment fails immediately. Right after "unpacking
archive" (~30 MB), the build dies with:
Error: Failed to read app source directory
Caused by: No such file or directory (os error 2)
nixpacks exited with an error
The source never reaches the builder — nixpacks can't read the app directory
after unpack, before install/build even starts.
Ruled out on my side:
-
The SAME repo builds fine in my PRODUCTION environment (last success 4ac92a8),
with identical service config.
-
Fails on BOTH a GitHub push AND
railway up(two different upload paths). -
Fails on two different Metal builders: builder-pjzljv (US) and builder-cnefny (EU West).
-
Tried both regions (was US, moved to EU West) — no change.
-
Root Directory is empty; Nixpacks set via /railway.json (build: npm run build).
-
No incident on your status page. Auto-deploy on, Wait for CI off.
-
Your own "Diagnose" on the failed deployment also fails.
Failed deployment IDs: e31589e (git), c57355d4 / 89b74f16 / 67c7456a (railway up).
Please repair the source provisioning / environment state for this service so
builds can read the source again.
1 Replies
41 minutes ago
The Root Directory setting on this service in the staging environment is set to https://github.com/MarcusFresh84/opus_tutti.git (the full repo URL) instead of being empty. Nixpacks is treating that string as a filesystem path to look for after unpack, which does not exist, hence the "os error 2". Your production environment has this field empty, which is why it works there. Clear the Root Directory field in the staging service settings, apply the change, and the build will proceed.
Status changed to Awaiting User Response Railway • 41 minutes ago