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

• 🧵 No interpreter found for Python
• 🧵 Build failing for new deployments, was working before
• 🧵 loading secrets failed to authorize
• 🧵 build error running python activating venv and installing requirements.txt

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

hello? any help?

this is a railway issue not my project issue.... previous build that worked for 2 months crash on redeploy now nothing changed. deleting our subscription if this isn't fixed asap

Having the same issue right now, did you find out what was causing?

I just checked and it seems Docker is having an outage, which seems to be the culprit on my end.

I fixed it by specifying a different node version in my package file

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

Same thing for me right now. Inexplicable errors in the otherwise tried and true deploy process.

This worked with node 23

This is the error I am getting, may be an issue with the package signature:

---

mise pnpm@9.15.9 install

mise node@22.18.0 install

mise node@22.18.0 download node-v22.18.0-linux-x64.tar.gz

mise pnpm@9.15.9 download pnpm-linux-x64

gpg: Signature made Thu Jul 31 21:47:23 2025 UTC gpg: using EDDSA key 5BE8A3F6C8A5C01D106C0AD820B1A390B168D356 gpg: Can't check signature: No public key

mise ERROR gpg failed gpg: Signature made Thu Jul 31 21:47:23 2025 UTC gpg: using EDDSA key 5BE8A3F6C8A5C01D106C0AD820B1A390B168D356 gpg: Can't check signature: No public key

mise pnpm@9.15.9 extract pnpm-linux-x64

mise pnpm@9.15.9 ✓ installed

mise ERROR failed to install core:node@22.18.0 mise ERROR gpg exited with non-zero status: exit code 2 mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

[railpack] copy secrets hash

Cached

[railpack] hash used secrets

Cached

[railpack] copy used secrets hash

Based on your feedback, the move to node 23 could resolve it if the package's signature is valid and verifiable.

Same issue here trying to deploy a Next.js app that was successfully deployed yesterday... Needs to be fixed asap

We see the issue and are working on a fix. The problem has to do with Node 22.18.0 (the latest LTS version) not having a public key that Mise can verify. You can specify the previous version (22.17.0) or wait for a workaround that we will have soon.

https://nodejs.org/en/blog/release/v22.18.0

This Node version was released yesterday and I'm unsure why it is missing a verifiable public key. But we will look into it so we can prevent these errors in the future.

That worked, thanks!

Thanks, please respond to the thread so we can return to the latest when done. Thanks a lot.

A fix has been released. You should be able to build with 22.18.0 now