Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

package 404 not found #1626

Closed
es5es5 opened this issue Aug 6, 2020 · 60 comments
Closed

package 404 not found #1626

es5es5 opened this issue Aug 6, 2020 · 60 comments

Comments

@es5es5
Copy link

es5es5 commented Aug 6, 2020

What / Why

Your package manager couldn't get any packages. (404 not found)

When

Now

Where

  • npm public registry

How

  • n/a

Current Behavior

404 not found

image

@Abjuk
Copy link

Abjuk commented Aug 6, 2020

The same

@es5es5 es5es5 changed the title [BUG] <title> package 404 not found Aug 6, 2020
@ckimy
Copy link

ckimy commented Aug 6, 2020

It seems it cannot find all the scoped packages.

@iTaybb
Copy link

iTaybb commented Aug 6, 2020

Same here.

@shane-deveire
Copy link

Same here, all vue cli packages for example are 404ing

@eraldoforgoli
Copy link

I'm having this problem too

@aster-17
Copy link

aster-17 commented Aug 6, 2020

same here

@TryingOutSomething
Copy link

I believe there's another issue that is similar

Duplicate of #1624

@Naveen604
Copy link

Facing the same. even using npm install getting the same error

@wtlin1228
Copy link

same here

@averkij
Copy link

averkij commented Aug 6, 2020

Confirm.

@MrTomek
Copy link

MrTomek commented Aug 6, 2020

https://status.npmjs.org/

@ripkens
Copy link

ripkens commented Aug 6, 2020

Even if it states its resolved partly, here you get another hint to follow:

Not Found - GET https://registry.npmjs.org/@protobufjs%2fbase64 - Not found

@BankNatthapon
Copy link

+1 we're waiting for your resolved npm team! hang in there✌️

@zszoubair
Copy link

same

@AlexAndBear
Copy link

same.
Holidays incoming!

@gotoinc
Copy link

gotoinc commented Aug 6, 2020

we can only wait for resolve issues

@Ademking
Copy link

Ademking commented Aug 6, 2020

same

@phanvungoc
Copy link

An unexpected error occurred: "https://registry.yarnpkg.com/@react-navigation/stack/-/stack-5.2.10.tgz: Request failed "404 Not Found"".

@lebowvsky
Copy link

Same! Unable to init a new Angular project...

@rbdhack
Copy link

rbdhack commented Aug 6, 2020

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@material-ui%2fcore - Not found

@dakairus
Copy link

dakairus commented Aug 6, 2020

any solution time? screwed in the middle of a production deployment. Any scoped npm package is failing

@H-Haynes
Copy link

H-Haynes commented Aug 6, 2020

now ,its fixed

@rushhourmedia
Copy link

Still not fixed for me!

@markb-trustifi
Copy link

This is critical error. No scoped packages can be downloaded.
For example, packages like:
"@kenjiuno/decompressrtf": "^0.1.2",
"@kenjiuno/msgreader": "^1.2.5",
"@peculiar/webcrypto": "^1.0.8",

@Ademking
Copy link

Ademking commented Aug 6, 2020

now ,its fixed

No it's not

@shi-rudo
Copy link

shi-rudo commented Aug 6, 2020

same here, 404 on everything scoped

@kuperchal
Copy link

Same here, almost for an hour for now.
Any updates on solving time?

@IanMoroney
Copy link

@NeilCresswell
Copy link

Getting this on many dozens of unrelated packages, many of which are dependencies of some major projects. In case there is some region CDN issue, I tried using a VPN to appear to be in a different continent but that didn't make any difference. Sometimes a package is present but is not the latest released but one from a long time ago. Sometimes a package is not present. Tried various tricks like changing NPM version, npm config set registry http://registry.npmjs.org, etc. but no luck. Does appear to be a registry issue.

Am dead in the water on all my projects right now and no longer able to install packages like Cordova for example.

@korki43
Copy link

korki43 commented Aug 6, 2020

@NeilCresswell it's an issue in the registry. See here: https://status.npmjs.org/

@NeilCresswell
Copy link

@NeilCresswell it's an issue in the registry. See here: https://status.npmjs.org/

@korki43 Thanks. I saw your post above right after I submitted mine and have added status.npmjs.org to my bookmarks.

@nicoWeb31
Copy link

ok i'm not alone....

@VAlgazin
Copy link

VAlgazin commented Aug 6, 2020

The big day when deploy is not available)

@akacanet87
Copy link

This reminds me last year.. Maybe it was almost this season, wasn't it??

@arham09
Copy link

arham09 commented Aug 6, 2020

same here,

@wahyualfarisi
Copy link

Yes, I Have same issue

@gilberto1991
Copy link

Same problem here

@arpalmares
Copy link

Same here. Cannot globally install serverless.

npm install serverless -g

image

@BankNatthapon
Copy link

BankNatthapon commented Aug 6, 2020

Latest update! they're continuing to work on a fix for this issue: https://status.npmjs.org/incidents/cksjqc1w11v5

@TiagoPortfolio
Copy link

I didn't find many NPM registry alternatives but while this is not fixed I am using this one:

npm install --registry http://registry.npm.taobao.org
yarn install --registry http://registry.npm.taobao.org

@dandelio
Copy link

dandelio commented Aug 6, 2020

Same problem here

@grygoryz
Copy link

grygoryz commented Aug 6, 2020

Same problem. Can't install creat-react-app and create-next-app because of it

@pavazmo
Copy link

pavazmo commented Aug 6, 2020

I think it's fixed ( at least in my case)

@jpdewing
Copy link

jpdewing commented Aug 6, 2020

fixed for me too

@arpalmares
Copy link

Already working! THANK YOU!

@oxowl
Copy link

oxowl commented Aug 6, 2020

Yes, working! tks!

@wildmichael
Copy link

I still have the issue:

$ npm i @tuxc/long
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tuxc%2flong - Not found
npm ERR! 404
npm ERR! 404  '@tuxc/long@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

@coolbeans47
Copy link

I still have the issue with AWS amplify builds.

@1000i100
Copy link

1000i100 commented Aug 6, 2020

@darcyclarke
Copy link
Contributor

darcyclarke commented Nov 5, 2020

Of note, a 404 response is not uncommon to experience when there is a misconfiguration in your env & you're making requests to private/scoped packages; That said, this issue seemed to occur during a partial outage back in August, so I'm going to assume this has been resolved for the bulk of folks since that incident, & close accordingly.

If you continue to experience any issues with the npm registry, website or any other service in the future, please...

  • check the status of those services (ie. npm ping or https://status.npmjs.org/ or https://twitter.com/npm_support)
  • check your environment config (ie. npm config ls or cat ~/.npmrc etc.)
  • check to see if you're logged in - only, if you're trying to access private/scoped packages (ie. npm whoami)

If everything looks right & you've still got issues/errors, you can file a ticket here: https://www.npmjs.com/support

This repo's issues are meant to capture bugs within the npm client itself. If you think you've found a bug, please open an issue using one of our templates here: https://github.com/npm/cli/issues/new/choose For any other support, you can head over to https://npm.community to find the links I noted above along with references to documentation, our public events calendar, legacy/archived forums etc..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests