Protobuf 404 on npm install (package dependencies and npm i) #1056

dannypaz · 2018-05-29T23:04:14Z

protobufjs is being installed via dependencies from grpc however I am unable to install protobufjs standalone as well.

Time of issue: 4:03pm PST

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^5.0.0

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@6.8.6

EDIT for full stack

2 info using npm@6.1.0
3 info using node@v8.11.1
4 verbose npm-session 7bed9828e33a7a1f
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 404 https://registry.npmjs.org/protobufjs 210ms
8 silly fetchPackageMetaData error for protobufjs@6.8.6 404 Not Found: protobufjs@6.8.6
9 timing stage:rollbackFailedOptional Completed in 1ms
10 timing stage:runTopLevelLifecycles Completed in 437ms
11 verbose stack Error: 404 Not Found: protobufjs@6.8.6

I'm currently 404ing with npm i protobufjs@5.0.0 and npm i protobufjs. Im not sure if this is an issue w/ npm but wanted to give yall a headsup.

The text was updated successfully, but these errors were encountered:

rfk91 · 2018-05-29T23:06:22Z

Same here. It was working like an hour ago, but now it is not.
https://registry.npmjs.org/protobufjs works, but it may be some internal npm issue.

ghost · 2018-05-29T23:08:11Z

Same here

SippieCup · 2018-05-29T23:08:16Z

Same here, although I'm stuck on the extremely outdated protobufjs@^3.5.0. Thanks pkgcloud.

It went down sometime after 5:50 PM EST.

jwahlin · 2018-05-29T23:08:55Z

It's not just npm. I have the same issue with yarn add protobufjs.

daywednes · 2018-05-29T23:09:43Z

same here :) i'm looking forward to the fix.

Negan1911 · 2018-05-29T23:46:42Z

Same here :/

dcodeIO · 2018-05-29T23:48:42Z

Very strange. There haven't been any updates to the package for 14 days, so my assumption for now is that this is some sort of npm issue.

Negan1911 · 2018-05-29T23:49:35Z

@dcodeIO i guess that could be related with this?
https://status.npmjs.org/

Do you mind to republish your package?

dcodeIO · 2018-05-30T00:08:56Z

Yeah, except that the package hasn't been updated between "Monday night and Tuesday morning".

issackpgit · 2018-05-30T00:30:05Z

Same here

fabiofgpavan · 2018-05-30T00:38:19Z

Same here

npm ERR! 404 Not Found: protobufjs@^5.0.3

bradysheridan · 2018-05-30T00:40:17Z

+1

nickpestov · 2018-05-30T00:48:57Z

Doing npm cache clean --force fixed the issue for me.

bruno-visor · 2018-05-30T00:58:35Z

I am facing the same issue, there is a problem with npm, I temporary solved the problem by downgrading the NPM with this code
.....
"engines": {
"npm": "4.6.1"
},... - package.json

jporsay · 2018-05-30T01:20:41Z

Never mind, it's working now =D

Original:

@nickpestov Not here unfortunately

  1.7.0

Node version: 
  8.9.4

Platform: 
  darwin x64

Trace: 
  Error: https://registry.yarnpkg.com/protobufjs: Not found
      at Request.params.callback [as _callback] (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:65656:18)
      at Request.self.callback (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:134675:22)
      at emitTwo (events.js:126:13)
      at Request.emit (events.js:214:7)
      at Request.<anonymous> (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:135658:10)
      at emitOne (events.js:116:13)
      at Request.emit (events.js:211:7)
      at IncomingMessage.<anonymous> (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:135578:12)
      at Object.onceWrapper (events.js:313:30)
      at emitNone (events.js:111:20)

Phineas · 2018-05-30T01:25:46Z

Same issue here, guessing it's just an npm failure. Horrible failure though, all my deployment pipelines failed earlier which caused my kubernetes pods to scale down making my service unavailable

khalilit · 2018-05-30T01:37:51Z

Same issue for me

xuanyue202 · 2018-05-30T01:41:17Z

I don't think yarn works. Maybe @nickpestov uses local cache?

> yarn add protobufjs@^5.0.0

yarn add v1.4.0
info No lockfile found.
[1/4] 🔍  Resolving packages...
error An unexpected error occurred: "Couldn't find package \"protobufjs\" on the \"npm\" registry.".
info If you think this is a bug, please open a bug report with the information provided in "/private/tmp/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

khalilit · 2018-05-30T01:44:27Z

Downgrade npm to version 4 via : npm cache clean --force + npm install -g npm@4 solved the problem and now npm i protobufjs@latest works fine

nickpestov · 2018-05-30T01:45:29Z

@jporsay & @xuanyue202, I was getting the 404 Not Found for protobufjs locally and npm cache clean --force seemed to fix the issue. But I am still experiencing the issue remotely (Google Cloud Builder).

artz · 2018-05-30T01:52:08Z

This issue is currently affecting me, using both npm and yarn fwiw.

1724 verbose stack Error: 404 Not Found: protobufjs@^6.8.0
1724 verbose stack     at fetch.then.res (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
1724 verbose stack     at tryCatcher (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
1724 verbose stack     at Promise._settlePromiseFromHandler (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
1724 verbose stack     at Promise._settlePromise (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
1724 verbose stack     at Promise._settlePromise0 (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
1724 verbose stack     at Promise._settlePromises (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
1724 verbose stack     at Async._drainQueue (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
1724 verbose stack     at Async._drainQueues (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
1724 verbose stack     at Immediate.Async.drainQueues (/Users/artz/.nvm/versions/node/v8.9.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
1724 verbose stack     at runCallback (timers.js:789:20)
1724 verbose stack     at tryOnImmediate (timers.js:751:5)
1724 verbose stack     at processImmediate [as _immediateCallback] (timers.js:722:5)
1725 verbose cwd /Users/artz/Sites/lightbox
1726 verbose Darwin 17.5.0
1727 verbose argv "/Users/artz/.nvm/versions/node/v8.9.1/bin/node" "/Users/artz/.nvm/versions/node/v8.9.1/bin/npm" "install"
1728 verbose node v8.9.1
1729 verbose npm  v5.6.0
1730 error code E404
1731 error 404 Not Found: protobufjs@^6.8.0
1732 verbose exit [ 1, true ]

raman2072 · 2018-05-30T01:53:43Z

This is NOT fixed. I tried 5 minutes ago.

npm WARN deprecated nodemailer@2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated mailcomposer@4.0.1: This project is unmaintained
npm WARN deprecated socks@1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated buildmail@4.0.1: This project is unmaintained
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^5.0.3

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-05-30T01_21_58_490Z-debug.log
"
Command failed

artz · 2018-05-30T01:53:57Z

Also fwiw, to reproduce:

npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.


npm install @google-cloud/language
npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^6.8.0

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/artz/.npm/_logs/2018-05-30T01_53_33_243Z-debug.log

xuanyue202 · 2018-05-30T01:55:33Z

@nickpestov I tried your solution but no luck :(

➜  /tmp npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
➜  /tmp npm install protobufjs@^5.0.0
npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^5.0.0

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/yaoliang/.npm/_logs/2018-05-30T01_54_00_021Z-debug.log

rahulk-kikani · 2018-05-30T02:05:03Z

Same here!

npm install protobufjs

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@latest

raman2072 · 2018-05-30T02:13:08Z

Why is this NOT yet reported in https://status.npmjs.org/? According to the site apparently there are no issues?

trusktr · 2018-05-30T02:24:11Z

I emailed them shortly after posting #1057, but no reply yet.

eyexx · 2018-05-30T02:38:29Z

same here.

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^5.0.0

when i try npm install firebase, i faced this issue

ravihugo · 2018-05-30T03:35:24Z

Is this taobao safe?

xuanyue202 · 2018-05-30T04:09:59Z

This taobao is a repo mirror run by Alibaba which aims to solve the network problem from China to npmjs. Personally I think it is ok, but it is no more than a temporary solution.

KeanuTomatoMomotaro · 2018-05-30T04:19:40Z

I just tried installing the module normally. The original registry seems to be running now.

NPM version 6.1.0
Node Version 8.10.0

ravihugo · 2018-05-30T04:27:49Z

Confirmed, it works without using the alternative registry.

ghost · 2018-05-30T04:40:57Z

Confirmed as well. But I'm curious, what happened?

And also, how to prevent what happened to @Phineas

all my deployment pipelines failed earlier which caused my kubernetes pods to scale down making my service unavailable

rendaw · 2018-05-30T11:34:36Z

Still not working here:

$ yarn add protobufjs@6.7.3
...
error An unexpected error occurred: "https://registry.npmjs.org/protobufjs/-/protobufjs-6.7.3.tgz: Request failed \"404 Not Found\"".

yarn add protobufjs works though. This is part of a complex build process in a dependency so changing the registry/version to work around won't be easy.

supermacro · 2018-05-30T11:39:08Z

Maybe we can close this issue and open an issue within NPM's repo?

https://github.com/npm/npm

rendaw · 2018-05-30T11:55:07Z

npm/npm#20809

trusktr · 2018-05-30T16:04:13Z

They emailed back 30 min ago:

Thanks for reaching out and for the heads up. Our ops team believe they've identified the issue with the protobufjs package. We rolled out a fix last evening. We believe all versions of the package should once again be available.

rendaw · 2018-05-30T16:24:26Z

@trusktr is there any public discussion of this? I just checked and still getting 404:

$ npm install protobufjs@6.7.3
...
npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@6.7.3

I suppose it could be some issue with edge caches but the text seems to imply that it's been 8+ hours since they resolved it.

supermacro · 2018-05-30T17:31:00Z

I got a twitter reply:

link: https://twitter.com/npm_support/status/1001877600690679811

daywednes · 2018-05-30T19:50:24Z

can i get a npm loves you tweet? lol

dannypaz · 2018-05-31T06:26:36Z

Closing this issue as this particular 404 case looks to be resolved. If anyone continues to have problems, feel free to comment or open another issue.

scream314 · 2018-05-31T15:32:54Z

I do not think it is resolved:

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@https://registry.npmjs.org/protobufjs/-/protobufjs-4.1.3.tgz

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-05-31T15_29_30_145Z-debug.log

Strangely if I try to open https://registry.npmjs.org/protobufjs/-/protobufjs-4.1.3.tgz in a browser, it starts to download the tgz...

mattrcullum · 2018-05-31T21:05:33Z

When I open https://registry.npmjs.org/protobufjs/-/protobufjs-4.1.3.tgz it gives me an error page. I'm also unable to install @ google-cloud/speech which uses protobufjs-6.8.6

rdlowrey · 2018-06-01T00:41:03Z

I've been npm installing all evening and this just started happening to me in the last ~20 minutes as well.

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@6.8.6

Update: npm cache clean --force did NOT help.

jwahlin · 2018-06-01T00:54:31Z

Just started happening to me (again) about 20 minutes ago.

kylehotchkiss · 2018-06-01T00:55:53Z

It's back! Tweet @npm_support about it if you are also experiencing https://twitter.com/npm_support/status/1001877600690679811

aalexand · 2018-06-01T01:11:27Z

Experiencing it too.

rohitjmath · 2018-06-01T01:11:39Z

me too

kylehotchkiss · 2018-06-01T01:19:52Z

https://twitter.com/npm_support/status/1002354019355037697 they've alerted ops team

tmauricio · 2018-06-01T01:25:30Z

me too, i wait the solution

shaunpersad · 2018-06-01T01:31:11Z

This really is a sad state of affairs. NPM has become a single point of failure for build processes everywhere. This package is downloaded about 115k times a week. There must be a better way to get high availability on packages, especially essential ones!

tmauricio · 2018-06-01T01:51:49Z

fix it!!!!

briandeheus · 2018-06-01T02:00:18Z

if you're running into this issue when you need to install both private and public packages:

npm install protobufjs@5 --registry https://registry.npm.taobao.org
npm install

The second time around npm will notice profobufjs is installed and won't attempt to re-install it...

edahood · 2018-06-01T02:08:00Z

So https://registry.npmjs.org/protobufjs/-/protobufjs-4.1.3.tgz Still fails, but
http://registry.npmjs.org/protobufjs/-/protobufjs-4.1.3.tgz Seems to be the right file

Unfortunately, this is a dependency of a dependency of a dependency, and i think one is using shrink wrap.
Really not sure what to do to fix this quickly

scream314 · 2018-06-01T14:20:10Z

The 404 was gone after I switched from npm 5.6.0 to npm 6.x.x. But this introduced a bunch of other issues.
But finally I was able to install all my dependencies... by installing and using yarn ;)

Negan1911 mentioned this issue May 29, 2018

error 404, unable to install protobufjs #1057

Closed

djedi mentioned this issue May 30, 2018

NPM Error Vheissu/aurelia-firebase-ssr-starter#2

Closed

rendaw mentioned this issue May 30, 2018

npm ERR! 404 Not Found: protobufjs@^6.8.6 npm/npm#20809

Open

5 tasks

dannypaz closed this as completed May 31, 2018

3z3qu13l mentioned this issue Jun 1, 2018

Update pkgcloud dependency vulnerabilities pkgcloud/pkgcloud#609

Open

Protobuf 404 on npm install (package dependencies and npm i) #1056

Protobuf 404 on npm install (package dependencies and npm i) #1056

Comments

dannypaz commented May 29, 2018 • edited

rfk91 commented May 29, 2018 • edited

ghost commented May 29, 2018

SippieCup commented May 29, 2018 • edited

jwahlin commented May 29, 2018

daywednes commented May 29, 2018

Negan1911 commented May 29, 2018

dcodeIO commented May 29, 2018

Negan1911 commented May 29, 2018

dcodeIO commented May 30, 2018

issackpgit commented May 30, 2018

fabiofgpavan commented May 30, 2018

bradysheridan commented May 30, 2018

nickpestov commented May 30, 2018

bruno-visor commented May 30, 2018 • edited

jporsay commented May 30, 2018 • edited

Phineas commented May 30, 2018

khalilit commented May 30, 2018

xuanyue202 commented May 30, 2018 • edited

khalilit commented May 30, 2018 • edited

nickpestov commented May 30, 2018

artz commented May 30, 2018

raman2072 commented May 30, 2018

artz commented May 30, 2018 • edited

xuanyue202 commented May 30, 2018

rahulk-kikani commented May 30, 2018 • edited

raman2072 commented May 30, 2018

trusktr commented May 30, 2018

eyexx commented May 30, 2018

ravihugo commented May 30, 2018

xuanyue202 commented May 30, 2018

KeanuTomatoMomotaro commented May 30, 2018

ravihugo commented May 30, 2018

ghost commented May 30, 2018 • edited by ghost

rendaw commented May 30, 2018

supermacro commented May 30, 2018

rendaw commented May 30, 2018

trusktr commented May 30, 2018 • edited

rendaw commented May 30, 2018 • edited

supermacro commented May 30, 2018

daywednes commented May 30, 2018

dannypaz commented May 31, 2018 • edited

scream314 commented May 31, 2018 • edited

mattrcullum commented May 31, 2018 • edited

rdlowrey commented Jun 1, 2018 • edited

jwahlin commented Jun 1, 2018

kylehotchkiss commented Jun 1, 2018

aalexand commented Jun 1, 2018

rohitjmath commented Jun 1, 2018

kylehotchkiss commented Jun 1, 2018

tmauricio commented Jun 1, 2018

shaunpersad commented Jun 1, 2018

tmauricio commented Jun 1, 2018

briandeheus commented Jun 1, 2018

edahood commented Jun 1, 2018

scream314 commented Jun 1, 2018

dannypaz commented May 29, 2018 •

edited

rfk91 commented May 29, 2018 •

edited

SippieCup commented May 29, 2018 •

edited

bruno-visor commented May 30, 2018 •

edited

jporsay commented May 30, 2018 •

edited

xuanyue202 commented May 30, 2018 •

edited

khalilit commented May 30, 2018 •

edited

artz commented May 30, 2018 •

edited

rahulk-kikani commented May 30, 2018 •

edited

ghost commented May 30, 2018 •

edited by ghost

trusktr commented May 30, 2018 •

edited

rendaw commented May 30, 2018 •

edited

dannypaz commented May 31, 2018 •

edited

scream314 commented May 31, 2018 •

edited

mattrcullum commented May 31, 2018 •

edited

rdlowrey commented Jun 1, 2018 •

edited