raphaelyancey commented 4 years ago

What / Why

I'm getting E429 error

When

Everytime I run npm ci (since today at least)

Where

npm public registry

Current Behavior

The npm ci command returns E429 error (Too Many Requests) and doesn't complete packages installation

Steps to Reproduce

npm ci

Expected Behavior

It should install packages

44kia244 commented 4 years ago

Same here, but with npm -g install @vue/cli.

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/lowdb/-/lowdb-1.0.0.tgz

hsmusz commented 4 years ago

805 similar isseue - random 403 or 429

MatejBalantic commented 4 years ago

Having same issue on our pipelines. Responses vary between 403 Forbidden and 420 Too Many Requests

kurrestahlberg commented 4 years ago

We see this in any of our CI tasks running in AWS

Step 8/11 : RUN npm ci
 ---> Running in 87051ac87a51
npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/@types/xxhashjs/-/xxhashjs-0.2.1.tgz
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-02-17T11_49_35_151Z-debug.log
The command '/bin/sh -c npm ci' returned a non-zero code: 1
ERROR: Job failed: exit code 1

m33ch commented 4 years ago

Also for me on bamboo build:

error   17-feb-2020 12:49:46    npm ERR! code E429
error   17-feb-2020 12:49:46    npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/@snyk/configstore/-/configstore-3.2.0-rc1.tgz

quite commented 4 years ago

Centralized infrastructure :~( (waiting for the post-mortem, but not holding my breath...)

raphaelyancey commented 4 years ago

It'd be useful to have a list of (verified) public registry mirrors. I found some but I can't trust them.

pwright08 commented 4 years ago

Same, both locally and on Circle CI

Kellym-Kainos commented 4 years ago

Also seeing the same using Circle CI and locally

npm ERR! code E429 npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/camelcase/-/camelcase-2.1.1.tgz

jimhooker2002 commented 4 years ago

I'm seeing errors like..

"The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website"

and

"You are being rate limited"

I'm guessing this is all related?

ymynem commented 4 years ago

We are also having this issue when deploying on Heroku.

npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz

bitqueenbr commented 4 years ago

Having the same errors when deploying on heroku.

codyfy commented 4 years ago

same here with AWS CodeBuild and npm i -g aws-cdk

npm ERR! code E429

28 | npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/aws-cdk

general server issue?

esrgrlk commented 4 years ago

I also have same problem npm ERR! code E429 npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/silent-error

vrease commented 4 years ago

Same here when installing packages locally. Sweden.


npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/lodash

mattandrews commented 4 years ago

Yep, I'm seeing this on Travis too for npm audit:

npm ERR! audit Your configured registry (https://registry.npmjs.org/) may not support audit requests, or the audit endpoint may be temporarily unavailable.

npm ERR! audit The server said:

Access denied | registry.npmjs.org used Cloudflare to restrict access
You are being rate limited
The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website.

Franchi05 commented 4 years ago

Same thing happening over here. Getting the error when doing npm update

wiseelf commented 4 years ago

17-Feb-2020 11:47:48 npm ERR! code E429 17-Feb-2020 11:47:48 npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.8.3.tgz

Same issue here. We are using bamboo ci. Own installation. The file is accessible from the server itself:


--2020-02-17 11:59:28--  https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.8.3.tgz
Resolving registry.npmjs.org (registry.npmjs.org)... 104.16.17.35, 104.16.24.35, 104.16.26.35, ...
Connecting to registry.npmjs.org (registry.npmjs.org)|104.16.17.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6735 (6.6K) [application/octet-stream]
Saving to: 'plugin-transform-block-scoping-7.8.3.tgz'

plugin-transform-block-scoping-7.8.3.tgz                 100%[================================================================================================================================>]   6.58K  --.-KB/s    in 0s

2020-02-17 11:59:28 (95.5 MB/s) - 'plugin-transform-block-scoping-7.8.3.tgz' saved [6735/6735]```

dtmzr commented 4 years ago

Facing this issue too, is this a global thing or maybe region related? We just had something similar last year in Germany.

dorsharon commented 4 years ago

Same here running on Gitlab CI

simonkarman commented 4 years ago

Same here in The Netherlands. (AWS Codebuild from Ireland)

serggend commented 4 years ago

Russia to

Volem commented 4 years ago

Istanbul here

NickThompson1993 commented 4 years ago

This appears to be a Cloudflare related issue to the registry.npmjs.org site.

got the following html response on update:

<!DOCTYPE html>
npm ERR! <!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
npm ERR! <!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
npm ERR! <!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
npm ERR! <!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
npm ERR! <head>
npm ERR! <title>Access denied | registry.npmjs.org used Cloudflare to restrict access</title>
npm ERR! <meta charset="UTF-8" />
npm ERR! <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
npm ERR! <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />
npm ERR! <meta name="robots" content="noindex, nofollow" />
npm ERR! <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1" />
npm ERR! <link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection" />
npm ERR! <!--[if lt IE 9]><link rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" type="text/css" media="screen,projection" /><![endif]-->
npm ERR! <style type="text/css">body{margin:0;padding:0}</style>
npm ERR!
npm ERR!
npm ERR! <!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script><!--<![endif]-->
npm ERR! <!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script><!--<![endif]-->
npm ERR!
npm ERR!
npm ERR!
npm ERR! </head>
npm ERR! <body>
npm ERR!   <div id="cf-wrapper">
npm ERR!     <div class="cf-alert cf-alert-error cf-cookie-error" id="cookie-alert" data-translate="enable_cookies">Please enable cookies.</div>
npm ERR!     <div id="cf-error-details" class="cf-error-details-wrapper">
npm ERR!       <div class="cf-wrapper cf-header cf-error-overview">
npm ERR!         <h1>
npm ERR!           <span class="cf-error-type" data-translate="error">Error</span>
npm ERR!           <span class="cf-error-code">1015</span>
npm ERR!           <small class="heading-ray-id">Ray ID: REDACTED &bull; 2020-02-17 11:26:27 UTC</small>
npm ERR!         </h1>
npm ERR!         <h2 class="cf-subheadline">You are being rate limited</h2>
npm ERR!       </div><!-- /.header -->
npm ERR!
npm ERR!       <section></section><!-- spacer -->
npm ERR!
npm ERR!       <div class="cf-section cf-wrapper">
npm ERR!         <div class="cf-columns two">
npm ERR!           <div class="cf-column">
npm ERR!             <h2 data-translate="what_happened">What happened?</h2>
npm ERR!             <p>The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website.</p>
npm ERR!           </div>
npm ERR!
npm ERR!
npm ERR!         </div>
npm ERR!       </div><!-- /.section -->
npm ERR!
npm ERR!       <div class="cf-error-footer cf-wrapper">
npm ERR!   <p>
npm ERR!     <span class="cf-footer-item">Cloudflare Ray ID: <strong>REDACTED</strong></span>
npm ERR!     <span class="cf-footer-separator">&bull;</span>
npm ERR!     <span class="cf-footer-item"><span>Your IP</span>: REDACTED</span>
npm ERR!     <span class="cf-footer-separator">&bull;</span>
npm ERR!     <span class="cf-footer-item"><span>Performance &amp; security by</span> <a href="https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span>
npm ERR!
npm ERR!   </p>
npm ERR! </div><!-- /.error-footer -->
npm ERR!
npm ERR!
npm ERR!     </div><!-- /#cf-error-details -->
npm ERR!   </div><!-- /#cf-wrapper -->
npm ERR!
npm ERR!   <script type="text/javascript">
npm ERR!   window._cf_translation = {};
npm ERR!
npm ERR!
npm ERR! </script>
npm ERR!
npm ERR! </body>
npm ERR! </html>

CormacWhite-rsc commented 4 years ago

Same issue happening with AWS Codebuild us-east-1. Was broken locally up til about 30 minutes ago but back working now (locally from Ireland)

merc1er commented 4 years ago

This appears to be a Cloudflare related issue to the registry.npmjs.org site.

Is there any mirror not using cloudflare?

tschannik commented 4 years ago

Same problem! Build pipelines are failing :(

jmeade11 commented 4 years ago

Same: npm ERR! code E429

ghost commented 4 years ago

That's it. Internet is done. Good bye everyone.

pedroac commented 4 years ago

I'm going to have lunch and hope this will be fixed when I return in less than an hour.

ahmatovicm commented 4 years ago

We can pretty much confirm that this IS an npm issue, yet on their status page everything is listed as operational. What is then the purpose of the npm status page?

marphi commented 4 years ago

The same issue. AWS from us-east-1

npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/archy/-/archy-1.0.0.tgz

dtmzr commented 4 years ago

Just reached out on twitter, 🤞 that we'll have information quickly.

roppazvan commented 4 years ago

Same...

andreisocaciu commented 4 years ago

npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/react-scripts/-/react-scripts-3.4.0.tgz

benchudev commented 4 years ago

same. Different packages, but keep getting 429 too many requests doing npm install and npm ci, since earlier today

16g commented 4 years ago

:(

shapeofarchitect commented 4 years ago

We are all down since morning now . NPM is broken. Dublin here

meikmenzel commented 4 years ago

Works fine for me now. 5$ / package. PM me.

bitqueenbr commented 4 years ago

Works fine for me now. 5$ / package. PM me.

so cheap

Hydrawisk793 commented 4 years ago

In south korea, I'm facing this issue too.

$ npm install --save-dev typescript
npm ERR! code E429
npm ERR! 429 Too Many Requests: loader-runner@2.4.0

Every NPM package just takes too much time to be installed. What happend to NPM?

AlexOlival commented 4 years ago

Lucky we just need to sit and wait Imagine if we were all construction workers, and suddenly all hammers stopped working around the world :thinking:

anton-bot commented 4 years ago

How about using the yarnpkg mirror for your builds?

mvakula commented 4 years ago

It's all fine http://status.npmjs.org/

16g commented 4 years ago

It's all fine http://status.npmjs.org/

mvakula commented 4 years ago

Indeed 😄

anton-bot commented 4 years ago

This discussion did not age well

https://github.com/yarnpkg/yarn/issues/5891

simonkarman commented 4 years ago

You could use: https://github.com/open-services/open-registry

# npm
npm config set registry https://npm.open-registry.dev

# yarn
yarn config set registry https://npm.open-registry.dev

Shinchy commented 4 years ago

Having the same issue in multiple environments (travis, local, server).

anton-bot commented 4 years ago

NPM: Nearly Perfect Mirror

npm / cli

[BUG] 429 Too Many Requests #836

What / Why

When

Where

Current Behavior

Steps to Reproduce

Expected Behavior

805 similar isseue - random 403 or 429

npm ERR! code E429