nodejs.org: 404 response for various Node.js downloads and pages

Cloudflare cached some incorrect 404 responses from our origin server in different physical locations. I’ve manually purged cached 404s for some popular downloads in all physical locations, but there might still be some 404 responses for certain files in certain locations. We expect these to be resolved soon.

We’re still investigating this together with CloudFlare, still monitoring.

I’m seeing 403s using Gradle (via faking an Ivy repo) both on CI and on my local development machine trying to hit nodejs.org/dist, and 404s from our Artifactory proxy.

Hey, y’all, as of now, we’ve done the last fixes that should have handled this incident. We’re posting updates on our Status page, and we’re going to follow up with a post-mortem afterwards. Thank you!

Unlocking tentatively. New information welcome. “I’m experiencing this issue too”-type posts are less helpful at this time. We are aware that a lot of people are experiencing this issue. Thanks.

Locking to avoid more people chiming in about having the same issue. Investigation is ongoing, lots of chatter in the nodejs-build channel on the OpenJS Slack if you want to follow along, or keep checking status.nodejs.org for updates, or keep checking this issue for updates. Thanks.

…and that file just started serving, in the last 15 seconds.

The same problem with version: v10.15.3

`What went wrong: Execution failed for task ‘:carelogic-webapp:nodeSetup’.

Could not resolve all dependencies for configuration ‘detachedConfiguration1’. Could not resolve org.nodejs:node:10.15.3. Required by: com.qualifacts.carelogic:carelogic-webapp:276.01 Could not GET ‘https://nodejs.org/dist/v10.15.3/ivy.xml’. Received status code 403 from server: Forbidden`

To add to @nschonni’s explanation, this route likely returned 404 before, and your tooling might have silently ignored that particular error code. The new firewall configuration blocks requests from some misconfigured Artifactory/Gradle setups that would otherwise cause unnecessary load on our infrastructure, resulting in status code 403.

@walec51 @SiWhite I have purged the cache for those files in all physical locations. (But don’t actually use those versions, they have long reached end-of-life status and are unsupported. Even 14.x reaches end-of-life next month.)

As I said in my previous comment, some rarely used files, especially those belonging to outdated and unsupported Node.js versions, may be unavailable in some physical locations for a few hours.

https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-x64.tar.gz <- still cannot be downloaded

you can download everything fom https://nodejs.org/dist/v10.16.3/ but the link above

I’m having the same issues with node-v16.15.0-linux-x64.tar.gz

getting 404 for https://nodejs.org/dist/v18.15.0/node-v18.15.0.pkg

Still see errors for https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz

The issue is not resolved for https://nodejs.org/dist/v16.14.0/node-v16.14.0-linux-x64.tar.gz

We’re still seeing elevated error rates in the last half-hour till now for https://nodejs.org/dist/v16.6.2/node-v16.6.2-linux-x64.tar.xz

Still seeing this for https://nodejs.org/dist/v16.17.1/node-v16.17.1-linux-x64.tar.xz.

The download issue should be recovering now and stable. Please let us know if you still see the issue.

I have the same problem with [https://nodejs.org/dist/v16.14.0/node-v16.14.0-linux-x64.tar.gz]

Thank you for the quick response! At least for me, the Issue appears to have been resolved (I’m now able to download the file I originally reported an issue with).

@ovflowd That is really good info, thank you! Looks like I can use that url to solve my current pain. Once I started poking around I was starting to see some CF cache headers.

For anyone else who may run into this:

NODEJS_ORG_MIRROR=https://direct.nodejs.org/dist/ asdf install nodejs x.y.z

seems to work - but let’s be responsible, node uses a CDN for a reason.

https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-arm64.tar.xz

https://direct.nodejs.org/dist/v18.13.0/node-v18.13.0-linux-arm64.tar.xz seems to be working fine. So double-down a CloudFlare cache issue.

I noticed that https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-arm64.tar.xz is 404ing

but these versions around it are not:

• https://nodejs.org/dist/v18.12.0/node-v18.12.0-linux-arm64.tar.xz
• https://nodejs.org/dist/v18.14.0/node-v18.14.0-linux-arm64.tar.xz
• https://nodejs.org/dist/v18.15.0/node-v18.15.0-linux-arm64.tar.xz

I only tried one download, but it was a 404 as well. But https://status.nodejs.org/ is all green so I must be HTTPing wrong. 😛