Deploy suddenly no longer installs Node.js 18 after minor edit

Support
1

Hello. My site was building fine today, but no longer builds. When it stopped building, I was testing some web-form edits to deploy preview #4 for https://6733b379ebf92e00083ced78--lively-rabanadas-79024f.netlify.app/

The build fails on initializing with a message: Failed to install Node.js version 18. But just one hour before, the same deploy preview built just fine with Node.js version 18.

I have copied two build logs below – one successful at 3PM, and a failed one at 4:50PM.

I would appreciate tips on what to do next. Thanks!

Successful build log at 3PM

2:59:16 PM: build-image version: 891f999a1a06f69441143b34bb0f6f9cee47b841 (focal)
2:59:16 PM: buildbot version: 891f999a1a06f69441143b34bb0f6f9cee47b841
2:59:16 PM: Fetching cached dependencies
2:59:16 PM: Starting to download cache of 216.8MB
2:59:17 PM: Finished downloading cache in 1.497s
2:59:17 PM: Starting to extract cache
2:59:20 PM: Finished extracting cache in 2.387s
2:59:20 PM: Finished fetching cache in 3.951s
2:59:20 PM: Starting to prepare the repo for build
2:59:20 PM: Preparing Git Reference pull/4/head
2:59:22 PM: Starting to install dependencies
2:59:22 PM: Started restoring cached mise cache
2:59:23 PM: Finished restoring cached mise cache
2:59:23 PM: Attempting Python version ‘3.8’, read from environment
2:59:24 PM: mise python@3.8.20 installing
2:59:24 PM: mise python@3.8.20 Running python-build
2:59:24 PM: Downloading Python-3.8.20.tar.xz…
2:59:24 PM: → https://www.python.org/ftp/python/3.8.20/Python-3.8.20.tar.xz
2:59:26 PM: Installing Python-3.8.20…
3:00:48 PM: Installed Python-3.8.20 to /opt/buildhome/.local/share/mise/installs/python/3.8.20
3:00:48 PM: mise python@3.8.20 python --version
3:00:48 PM: mise python@3.8.20 Python 3.8.20
3:00:48 PM: mise python@3.8.20 ✓ installed
3:00:48 PM: Python version set to 3.8
3:00:49 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:49 PM: Attempting Ruby version 2.7.2, read from environment
3:00:49 PM: Using Ruby version 2.7.2
3:00:50 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:50 PM: Started restoring cached go cache
3:00:50 PM: Finished restoring cached go cache
3:00:50 PM: go version go1.19.13 linux/amd64
3:00:50 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:50 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:51 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:51 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:51 PM: Using PHP version 8.0
3:00:51 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:51 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:51 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:52 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:52 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:52 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:00:52 PM: Started restoring cached Node.js version
3:00:57 PM: Finished restoring cached Node.js version
3:00:58 PM: v18.20.4 is already installed.
3:00:58 PM: Now using node v18.20.4 (npm v10.7.0)
3:00:58 PM: Enabling Node.js Corepack
3:00:58 PM: Started restoring cached build plugins
3:00:58 PM: Finished restoring cached build plugins
3:00:58 PM: Started restoring cached corepack dependencies
3:00:58 PM: Finished restoring cached corepack dependencies
3:00:58 PM: No npm workspaces detected
3:00:58 PM: Started restoring cached node modules
3:00:58 PM: Finished restoring cached node modules
3:00:58 PM: Installing npm packages using npm version 10.7.0
3:01:00 PM: > OpenCilk.org@1.0.0 postinstall
3:01:00 PM: > patch-package
3:01:00 PM: patch-package 6.5.1
3:01:00 PM: Applying patches…
3:01:00 PM: eleventy-plugin-toc@1.1.5 :heavy_check_mark:
3:01:00 PM: up to date, audited 461 packages in 1s
3:01:00 PM: 78 packages are looking for funding
3:01:00 PM: run npm fund for details
3:01:00 PM: 7 moderate severity vulnerabilities
3:01:00 PM: To address all issues (including breaking changes), run:
3:01:00 PM: npm audit fix --force
3:01:00 PM: Run npm audit for details.
3:01:00 PM: npm packages installed
3:01:00 PM: Successfully installed dependencies
3:01:00 PM: Starting build script
3:01:01 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:01:01 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:01:02 PM: Detected 1 framework(s)
3:01:02 PM: “eleventy” at version “1.0.2”
3:01:02 PM: Section completed: initializing
3:01:03 PM: ​
3:01:03 PM: Netlify Build
3:01:03 PM: ────────────────────────────────────────────────────────────────
3:01:03 PM: ​
3:01:03 PM: ❯ Version
3:01:03 PM: @netlify/build 29.55.5
3:01:03 PM: ​
3:01:03 PM: ❯ Flags
3:01:03 PM: accountId: 62506a101700c73c1d57d42b
3:01:03 PM: baseRelDir: true
3:01:03 PM: buildId: 6733b379ebf92e00083ced76
3:01:03 PM: deployId: 6733b379ebf92e00083ced78
3:01:03 PM: ​
3:01:03 PM: ❯ Current directory
3:01:03 PM: /opt/build/repo
3:01:03 PM: ​
3:01:03 PM: ❯ Config file
3:01:03 PM: /opt/build/repo/netlify.toml
3:01:03 PM: ​
3:01:03 PM: ❯ Context
3:01:03 PM: deploy-preview
3:01:03 PM: ​
3:01:03 PM: build.command from netlify.toml
3:01:03 PM: ────────────────────────────────────────────────────────────────
3:01:03 PM: ​
3:01:03 PM: $ npm run build
3:01:03 PM: > OpenCilk.org@1.0.0 build
3:01:03 PM: > npx @11ty/eleventy
3:01:04 PM: [/posts/2022-05-20-what-the-is-parallelism-anyhow/] Unknown term: “work” => /doc/reference/glossary/#work
3:01:04 PM: [/posts/2022-05-20-what-the-is-parallelism-anyhow/] Unknown term: “span” => /doc/reference/glossary/#span
3:01:04 PM: [/posts/2022-05-20-what-the-is-parallelism-anyhow/] Unknown term: “Parallelism” => /doc/reference/glossary/#parallelism
3:01:05 PM: {}
3:01:05 PM: [11ty] Copied 151 files / Wrote 58 files in 0.87 seconds (15.0ms each, v1.0.2)
3:01:05 PM: ​
3:01:05 PM: (build.command completed in 1.9s)
3:01:05 PM: ​
3:01:05 PM: Deploy site
3:01:05 PM: ────────────────────────────────────────────────────────────────
3:01:05 PM: ​
3:01:05 PM: Starting to deploy site from ‘_site’
3:01:05 PM: Calculating files to upload
3:01:05 PM: 32 new file(s) to upload
3:01:05 PM: 0 new function(s) to upload
3:01:06 PM: Starting post processing
3:01:06 PM: Post processing done
3:01:06 PM: Section completed: postprocessing
3:01:06 PM: Post processing - redirect rules
3:01:06 PM: Skipping form detection
3:01:06 PM: Post processing - header rules
3:01:06 PM: Site is live :sparkles:
3:01:06 PM: Section completed: deploying
3:01:06 PM: Site deploy was successfully initiated
3:01:06 PM: ​
3:01:06 PM: (Deploy site completed in 624ms)
3:01:06 PM: ​
3:01:06 PM: Netlify Build Complete
3:01:06 PM: ────────────────────────────────────────────────────────────────
3:01:06 PM: ​
3:01:06 PM: (Netlify Build completed in 2.6s)
3:01:06 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
3:01:06 PM: Caching artifacts
3:01:06 PM: Started saving node modules
3:01:06 PM: Finished saving node modules
3:01:06 PM: Started saving build plugins
3:01:06 PM: Finished saving build plugins
3:01:06 PM: Started saving mise cache
3:01:06 PM: Finished saving mise cache
3:01:06 PM: Started saving corepack cache
3:01:06 PM: Finished saving corepack cache
3:01:06 PM: Started saving pip cache
3:01:06 PM: Finished saving pip cache
3:01:06 PM: Started saving emacs cask dependencies
3:01:06 PM: Finished saving emacs cask dependencies
3:01:06 PM: Started saving maven dependencies
3:01:06 PM: Finished saving maven dependencies
3:01:06 PM: Started saving boot dependencies
3:01:06 PM: Finished saving boot dependencies
3:01:06 PM: Started saving rust rustup cache
3:01:06 PM: Finished saving rust rustup cache
3:01:06 PM: Started saving go dependencies
3:01:06 PM: Finished saving go dependencies
3:01:06 PM: Build script success
3:01:06 PM: Section completed: building
3:01:08 PM: Uploading Cache of size 217.9MB
3:01:09 PM: Section completed: cleanup
3:01:09 PM: Finished processing build request in 1m52.898s

Failed build log at 4:50PM

4:50:26 PM: build-image version: 891f999a1a06f69441143b34bb0f6f9cee47b841 (focal)
4:50:26 PM: buildbot version: 891f999a1a06f69441143b34bb0f6f9cee47b841
4:50:26 PM: Building without cache
4:50:26 PM: Starting to prepare the repo for build
4:50:26 PM: No cached dependencies found. Cloning fresh repo
4:50:26 PM: git clone --filter=blob:none GitHub - fastcode-ose/www.fastcode.org: Fastcode website
4:50:26 PM: Preparing Git Reference pull/4/head
4:50:29 PM: Starting to install dependencies
4:50:29 PM: Attempting Python version ‘3.8’, read from environment
4:50:30 PM: mise python@3.8.20 installing
4:50:30 PM: mise python@3.8.20 Running python-build
4:50:30 PM: Downloading Python-3.8.20.tar.xz…
4:50:30 PM: → https://www.python.org/ftp/python/3.8.20/Python-3.8.20.tar.xz
4:50:31 PM: Installing Python-3.8.20…
4:51:55 PM: Installed Python-3.8.20 to /opt/buildhome/.local/share/mise/installs/python/3.8.20
4:51:55 PM: mise python@3.8.20 python --version
4:51:55 PM: mise python@3.8.20 Python 3.8.20
4:51:55 PM: mise python@3.8.20 ✓ installed
4:51:55 PM: Python version set to 3.8
4:51:55 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:55 PM: Attempting Ruby version 2.7.2, read from environment
4:51:56 PM: Using Ruby version 2.7.2
4:51:56 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:57 PM: Started restoring cached go cache
4:51:57 PM: Finished restoring cached go cache
4:51:57 PM: go version go1.19.13 linux/amd64
4:51:57 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:57 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:57 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:57 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:57 PM: Using PHP version 8.0
4:51:57 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:58 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:58 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:58 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:58 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:58 PM: mise /opt/build/repo/mise.toml tools: python@3.8.20
4:51:59 PM: Downloading and installing node v18.20.5…
4:51:59 PM: Downloading https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz…
4:51:59 PM: curl: (22) The requested URL returned error: 404
4:51:59 PM: Binary download from https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz failed, trying source.
4:51:59 PM: grep: /opt/buildhome/.nvm/.cache/bin/node-v18.20.5-linux-x64/node-v18.20.5-linux-x64.tar.xz: No such file or directory
4:51:59 PM: Provided file to checksum does not exist.
4:51:59 PM: Binary download failed, trying source.
4:51:59 PM: Detected that you have 32 CPU core(s)
4:51:59 PM: Running with 31 threads to speed up the build
4:51:59 PM: Downloading https://nodejs.org/dist/v18.20.5/node-v18.20.5.tar.xz…
4:52:00 PM: Failed during stage ‘Install dependencies’: dependency_installation script returned non-zero exit code: 1
4:52:00 PM: curl: (22) The requested URL returned error: 404
4:52:00 PM: Binary download from https://nodejs.org/dist/v18.20.5/node-v18.20.5.tar.xz failed, trying source.
4:52:00 PM: grep: /opt/buildhome/.nvm/.cache/src/node-v18.20.5/node-v18.20.5.tar.xz: No such file or directory
4:52:00 PM: Provided file to checksum does not exist.
4:52:00 PM: Failed to install Node.js version ‘18’
4:52:00 PM: Failing build: Failed to install dependencies
4:52:00 PM: Finished processing build request in 1m34.123s

2

+1, had to change my project to Node 20 to be able to build

1 Like
3

Same issue on my end, too! Thanks for the tip, @fvieira – paid technical support explained what I knew (node.js 18 was down, please be patient). I didn’t notice you could change the node in your Site Configuration > Build & Deploy > Dependency Management. I changed it to 20 and all is looking well.

4

There is an explanation for this issue but Netlify is not the cause.

Nodejs.org bumped the latest release of version of 18 from 18.20.4 to 18.20.5 recently as documented here:

However, they also have non-working URLs for that version:

That URL above is a 404. This is the previous version which still works:

This issue is happening at nodejs.org and not at Netlify. Netlify cannot fix this issue because we do not control the nodejs.org website.

A workaround for this would be to pin the Node.js version used to 18.20.4 using one of the methods listed here:

However, if you do so, please remember revert that pinning to stay current once this incident is over.

As noted above, Node version 20 is not impacted by this issue to selecting that version will also resolve the issue.

5

hah, seems that Node posted the folder for 18.20.5: Index of /dist/v18.20.5/ but it only contains the SHA sums, not the actual code. Not ideal

6

Thanks Luke; I think that’s understandable for some of us, but new deploys pin to 18.20.5, the AI wasn’t very helpful (barked at a python issue), and there isn’t much documentation on a workaround or the reason for the node dependency (most of the support documents talk about using node in your projects, not that it’s a core need for netlify deployment). Searching for this issue sent me down a rabbit hole.

You’re right, it’s not Netlify’s fault node is down, but it is Netlify’s fault the need for node on deployment is not transparent. The logging was very helpful, though, and much appreciated. In Netlify’s defense, this looks to be impacting systems as far as Grammarly.

7

It was working completely fine. But suddenly I’m unable to deploy it on Netlify with the follow error.
Even a web app with just index file and css isn’t deploying.

Downloading https://nodejs.org/dist/v18.20.5/node-v18.20.5.tar.xz…

12:35:05 AM: curl: (22) The requested URL returned error: 404

12:35:05 AM: Binary download from https://nodejs.org/dist/v18.20.5/node-v18.20.5.tar.xz failed, trying source.

12:35:05 AM: grep: /opt/buildhome/.nvm/.cache/src/node-v18.20.5/node-v18.20.5.tar.xz: No such file or directory

12:35:05 AM: Provided file to checksum does not exist.

12:35:05 AM: Failed to install Node.js version ‘18’

12:35:05 AM: Failing build: Failed to install dependencies

8

I am facing the issue. Have you found a solution yet? This is hapenning with all our sites, which were perfectly working.

9

Hi, @SaadMirzaBaig and @andrewnforbes. The issue should be resolved now but it was not an issue that was caused by Netlify.

10

Thanks, Luke and all. As Luke said, the issue is resolved now (for me, anyway). I did nothing but wait, and now my site builds again.