404 response for various Node.js downloads and pages

URL:

https://nodejs.org/dist/v16.13.0/

Browser Name:

Chrome

Browser Version:

110.0.5481.177

Operating System:

MacOS 12.5.1

How to reproduce the issue:

Attempt to click link to download node-v16.13.0-darwin-x64.tar.gz from https://nodejs.org/dist/v16.13.0/
Expected to download file
Instead, get a 404 page

Using Chome

node-16.13.0-darwin-x64.mov

Using command line

$ wget https://nodejs.org/dist/v16.13.0/node-v16.13.0-darwin-x64.tar.gz

--2023-03-15 14:19:10--  https://nodejs.org/dist/v16.13.0/node-v16.13.0-darwin-x64.tar.gz
Resolving nodejs.org (nodejs.org)... 104.20.23.46, 104.20.22.46
Connecting to nodejs.org (nodejs.org)|104.20.23.46|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-03-15 14:19:10 ERROR 404: Not Found.

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. 😛

More seriously, it's the gzip files that seem broken so far. The "download now" link for me (linux x64) uses the xz file...and that link works. Too bad the asdf plugin for node wants the gz version. (Probably should be using xz anyway)

@ovflowd

@ovflowd The 404 is returning the new 404 page rather than the old nginx one, so I'm not sure if the new build isn't passing through a request correctly

/cc @nodejs/build

The only file that is giving 404 is https://nodejs.org/dist/v16.13.0/node-v16.13.0-darwin-x64.tar.gz so far. I've tried all other files of that directory and they're working.

The 404 is returning the new 404 page rather than the old nginx one, so I'm not sure if the new build isn't passing through a request correctly

Afaik we were always for every 404 within the server returning the Website 404. The only change we made was to also add the 404 to non-https requests.

@keithlayne

More seriously, it's the gzip files that seem broken so far. The "download now" link for me (linux x64) uses the xz file...and that link works. Too bad the asdf plugin for node wants the gz version. (Probably should be using xz anyway)

@keithlayne actually no, only one file is 404'ing. All other gz files are working.

@nodejs/build can we check why only https://nodejs.org/dist/v16.13.0/node-v16.13.0-darwin-x64.tar.gz this file is somehow 404'ing?

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:

@ovflowd

@ovflowd I was here becasue of this:

 ❯❯❯ asdf install nodejs 18.15.0
Trying to update node-build... ok
Downloading node-v18.15.0-linux-x64.tar.gz...
-> https://nodejs.org/dist/v18.15.0/node-v18.15.0-linux-x64.tar.gz
error: failed to download node-v18.15.0-linux-x64.tar.gz
-> https://nodejs.org/dist/v18.15.0/node-v18.15.0-linux-x64.tar.gz
error: failed to download node-v18.15.0-linux-x64.tar.gz

BUILD FAILED (Pop 22.04 using node-build 4.9.83-92-g23a7606c)

Binary installation failed; try compiling from source with `--compile` flag

So there are more problems than that one file.

@keithlayne

@keithlayne this seems to be a CloudFlare cache issue. You can check by accessing https://direct.nodejs.org/dist/v16.13.0/ which is the direct connection to our server, and all the links there work normally.

I know this doesn't solve your issue, but I'm checking with the team what are our options.

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

I can also check that this is being served directly within CloudFlare with curl -v

❯ curl -v https://nodejs.org/dist/v16.13.0/node-v16.13.0-darwin-x64.tar.gz
*   Trying 104.20.22.46:443...
* Connected to nodejs.org (104.20.22.46) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none

As 104.20.22.46 is a CloudFlare IP Address.

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.

@ovflowd

@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.

Please just a friendly reminder, avoid using direct.nodejs.org when possible. Our server sadly was not designed to handle the load that the web usually does to download Node.js 😅

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

Exactly! Thank you for your understanding 🙇

Is this from Artifactory? There is some filtering being put int place because of problems from a lot of misconfigured instances nodejs/build#3223

Our case was from Gradle too (specifically gradle-node-plugin, but I'm guessing the only significance is the plugin leads to a HEAD request, not just a GET.)

We've just fixed the issue by deploying a new CF Firewall rule.

I'm still seeing failed builds with respect to Ivy:


FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':project-theme-default:nodeSetup'.
> Could not resolve all files for configuration ':project-theme-default:detachedConfiguration1'.
   > Could not resolve org.nodejs:node:16.19.1.
     Required by:
         project :project-theme-default
      > Could not resolve org.nodejs:node:16.19.1.
         > Could not get resource 'https://nodejs.org/dist/v16.19.1/ivy.xml'.
            > Could not GET 'https://nodejs.org/dist/v16.19.1/ivy.xml'. Received status code 403 from server: Forbidden

https://nodejs.org/dist/v16.19.1/ivy.xml

That's a file that has never existed on the Node.js servers. Suggest you open up an issue on the Ivy plugin, as that would be an issue for their plugin

Also got the same problem since 17.3.2023:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':nodeSetup'.
> Could not resolve all files for configuration ':detachedConfiguration1'.
   > Could not resolve org.nodejs:node:12.22.6.
     Required by:
         project :
      > Could not resolve org.nodejs:node:12.22.6.
         > Could not get resource 'https://nodejs.org/dist/v12.22.6/ivy.xml'.
            > Could not GET 'https://nodejs.org/dist/v12.22.6/ivy.xml'. Received status code 403 from server: Forbidden

But also https://nodejs.org/dist/v12.22.6/ returns 500

@tomzi8571

@tomzi8571 as explained by @tridium-gward this is not an issue from our side. This file never existed and with the updated configuration it should now be properly handling the requests. So you have a misconfigured setup of your "Ivy"

@tomzi8571

@tomzi8571 as explained by @tridium-gward this is not an issue from our side. This file never existed and with the updated configuration it should now be properly handling the requests. So you have a misconfigured setup of your "Ivy"

Ok, but this configuration hasn't changed in years ... and this also broke Friday ...

@petty

As a result of triaging this issue, additional blocking rules were setup in nodejs/build#3223. This never worked, but previously didn't hard block as before @petty. This was always a misconfiguration, and won't be rolled back

@nschonni

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.

Ok, all good ... I just needed a newer version of the Gradle Node plugin (specifically moving from 1.3.0 to 1.5.3).

-    id 'com.github.node-gradle.node' version '1.3.0'
+    id 'com.github.node-gradle.node' version '1.5.3'

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`

@cjiga

@cjiga please, read prior comments before posting here.

I'm locking this issue to avoid duplicated comments and pings to the people here.

Navigation Menu

Repository navigation

404 response for various Node.js downloads and pages #5149

URL:

Browser Name:

Browser Version:

Operating System:

How to reproduce the issue:

Using Chome

Using command line

40 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

404 response for various Node.js downloads and pages #5149

Description

URL:

Browser Name:

Browser Version:

Operating System:

How to reproduce the issue:

Using Chome

Using command line

Activity

keithlayne commented on Mar 15, 2023

keithlayne commented on Mar 15, 2023

nschonni commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

blimmer commented on Mar 15, 2023

keithlayne commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

keithlayne commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

keithlayne commented on Mar 15, 2023

ovflowd commented on Mar 15, 2023

40 remaining items

ashsearle commented on Mar 17, 2023

ovflowd commented on Mar 17, 2023

petty commented on Mar 20, 2023

nschonni commented on Mar 20, 2023

tomzi8571 commented on Mar 20, 2023

ovflowd commented on Mar 20, 2023

petty commented on Mar 20, 2023

nschonni commented on Mar 20, 2023

tniessen commented on Mar 20, 2023

petty commented on Mar 20, 2023

cjiga commented on Mar 20, 2023

ovflowd commented on Mar 20, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions