nodejs.org denies access to zip files

[askingtherightquestion]

Hello everyone

Our git pipelines isn't able to access http://nodejs.org/dist/ since Saturday:

> Could not resolve all files for configuration ':detachedConfiguration1'.
   > Could not resolve org.nodejs:node:16.13.2.
     Required by:
         project :
      > Could not resolve org.nodejs:node:16.13.2.
         > Could not get resource 'http://nodejs.org/dist/v16.13.2/ivy.xml'.
            > Could not GET 'http://nodejs.org/dist/v16.13.2/ivy.xml'. Received status code 403 from server: Forbidden

The issue isn't caused by the missing ivy.xml. This issue suggests that the error is also thrown if the script isn't able to fetch the zip file: srs/gradle-node-plugin#292

This issue seems to impact other people / projects as well:

• https://github.com/nodejs/node/discussions/47124 (already closed)
• https://stackoverflow.com/questions/75795920/could-not-get-resource-https-nodejs-org-dist-v14-19-3-ivy-xml

One answer suggests that it might have something to do with DDNS prevention software installed by http://nodejs.org/. Does anyone face the same issue? Do you have any suggestions on how to solve this?

PS: The subfolders of http://nodejs.org/dist/ returned the HTTP error 500 a couple of hours ago. I tested this with different IPs and computers in order to make sure that I haven't been blocked or anything. Can I see somewhere if changes were done to the network of nodejs.org?

[targos]

I just checked in our Cloudflare logs and out of 1.14 million requests for zip files in the last 3 days, only 24 were blocked, all for the path /nodejs.org.sql.zip (and not from Gradle).

[UltraL0rd]

@askingtherightquestion did your update fix the problem? I'm stuck trying to build code that I need to get live

[askingtherightquestion]

I was able to resolve it by replacing the underlying node plugin we were using in gradle. Check if you have a build.gradle file in your project.

I had to replace classpath 'com.moowork.gradle:gradle-node-plugin:1.1.1' with classpath 'com.github.node-gradle:gradle-node-plugin:1.5.3'.

[UltraL0rd]

@askingtherightquestion already using classpath "com.github.node-gradle:gradle-node-plugin:2.2.4" still getting the ivy.xml error.

[UltraL0rd]

@targos Looks like my issue is slightly different from @askingtherightquestion . 2 days ago my pipelines on bitbucket and locally where still building fine. Yesterday evening my local and pipelines started producing the following errors :

Could not resolve org.nodejs:node:17.0.1.
Required by:
project :
> Could not resolve org.nodejs:node:17.0.1.
> Could not get resource 'https://nodejs.org/dist/v17.0.1/ivy.xml'.
> Could not GET 'https://nodejs.org/dist/v17.0.1/ivy.xml'. Received status code 403 from server: Forbidden

The version doesn't matter, they all throw the same error

[askingtherightquestion]

The maintainer of nodejs.org are referencing this comment as solution: srs/gradle-node-plugin#292 (comment)

I would just try out, if the version 2.2.0 works in a first step. The error happens within the plugin. It doesn't expect a 403 response.

The timing of your errors doesn't indicate that there were new changes. It worked maybe until yesterday, because of cached results (CDN, repository solution, local installation).