Hi, we're currently not running into any issues with our builders. What type of setup are you using to build ? seems everything broke after one commit but I'm unable to see detailed build logs. could you add a verbose option to the builds ?

Yes but this commit was rly trivial, but i can try to revert this commit to try. This morning the problem persist

Hi, following up, were you able to fix this ? We don't have any outage or known issue at the moment, so this is probably related to your build configuration/code.

I managed to work around the problem with a rollback and a re-deploy last time and it worked, so it wasn't a problem in my code...

Unfortunately the problem comes back and now even using rollbacks etc it's impossible to build while on my computer and on other hosting services it works fine.

Do you have a solution it's a bit urgent please.

It seems that I'm not the only one with this problem, in addition to the connection problem (getaddrinfo ENOTFOUND ...railway.internal)

I have the impression that the services keep things in cache which makes everything crash. We had this problem a few months ago and it was indeed a cache problem.

It seems like the build doesn't even launch.

As if the build crashes on launch and not during the build

Below is the error that persists:

>>> RUN --mount=type=cache,id=s/1612c81a-03f4-4d02-94bf-dd70da14a9f4-node_modules/cache,target=/app/node_modules/.cache nx build --project websockets

26 |

27 |

------------------- ERROR: failed to solve: process "/bin/bash -ol pipefail -c nx build --project websockets" did not complete successfully: exit code: 1

Error: Docker build failed

I add --verbose option on my builds
it seems there is a problem on requesting NX cloud
[stage-0 9/11] RUN --mount=type=cache,id=s/e93b1a3c-6a62-4017-82b5-7c7854793790-node_modules/cache,target=/app/node_modules/.cache nx build --project auth --verbose

Sep 02 14:51:25

Sep 02 14:51:26

#14 0.554 [NX CLOUD] Verifying current cloud bundle

Sep 02 14:51:26

Sep 02 14:51:26

#14 0.556 [NX CLOUD] A local bundle currently exists: { version: '2408.29.11', fullPath: '/app/.nx/cache/cloud/2408.29.11' }

Sep 02 14:51:26

#14 0.556 [NX CLOUD] Last verification was within the past 30 minutes, will not verify this time

Sep 02 14:51:26

#14 0.556 [NX CLOUD] Done: /app/.nx/cache/cloud/2408.29.11

Sep 02 14:51:26

Sep 02 14:51:26

#14 0.801

Sep 02 14:51:26

Sep 02 14:51:26

#14 0.806 > NX Received Code ERR_BAD_REQUEST. Retrying in 1s.

This seems to be an issue on nx cloud's side. Did you ensure everything is properly setup to work with it ?

As for the error connecting to redis, it likely comes from our private networking needing some time to bind in the legacy runtime (which your services are on). To fix this, you can either add a sleep 3 && in your start command, or switch to the v2 runtime from your services' settings.

Best,
Nico

This seems to be an issue on nx cloud's side. Did you ensure everything is properly setup to work with it ?

As for the error connecting to redis, it likely comes from our private networking needing some time to bind in the legacy runtime (which your services are on). To fix this, you can either add a sleep 3 && in your start command, or switch to the v2 runtime from your services' settings.

Best,
Nico

I have the exact same issue. My build has been up for a few months. I am trying to redeploy it and it is not working. We are trying to update some critical things. Please check my post and logs. I really need to sort this out asap.

Just checking in, has this been resolved?