`yarn` install 401 error for repository

[ErisDS]

yarn 0.22
OS mac OS 10.11.6

Trying to run yarn I get the following error:

Error: https://registry.yarnpkg.com/@glimmer/resolver/-/resolver-0.3.0.tgz: Request failed "401 Unauthorized"
      at Request.res (/Users/hannah/.yarn/lib-legacy/fetchers/tarball-fetcher.js:237:20)
      at emitOne (events.js:77:13)
      at Request.emit (events.js:169:7)
      at Request.onRequestResponse (/Users/hannah/.yarn/node_modules/request/request.js:1029:10)
      at emitOne (events.js:77:13)
      at ClientRequest.emit (events.js:169:7)
      at HTTPParser.parserOnIncomingClient (_http_client.js:433:21)
      at HTTPParser.parserOnHeadersComplete (_http_common.js:97:23)
      at TLSSocket.socketOnData (_http_client.js:322:20)
      at emitOne (events.js:77:13)
      at TLSSocket.emit (events.js:169:7)

Attempting to download the file via a browser works without fail. I've tried deleting node_modules and running yarn cache clear and am still seeing the issue.

Full yarn-error.log can be found here

[indatawetrust]

[ErisDS]

Yarn is working for me in the top level Ghost repository, but not in the Ghost-Admin git submodule.

Doing curl for the same package works:

curl -O https://registry.yarnpkg.com/@glimmer/resolver/-/resolver-0.3.0.tgz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19746  100 19746    0     0  19339      0  0:00:01  0:00:01 --:--:-- 19358

Even after a restart, reinstalling yarn, clearing the cache etc, I'm unable to install dependencies in the submodule, but the top level is still working.

I have no idea where to even start looking for this. I didn't have any problem before upgrading to 0.22.

[xdumaine]

We're getting 401's from Yarn for a namespaced module via .npmrc. Installs fine with npm, but yarn rejects with the 401. Tried cache clean and completely uninstalling yarn as well.

We did have this problem on 0.21.3 as well as 0.22. One dev on my team reported that it "just fixed itself" the next day.

[ErisDS]

This seemed to fix itself about an hour after I last posted.

I tried many things, and yarn in other locations was working fine. Doesn't make much sense to me.

[xdumaine]

I'm still blocked by this. Completely unable to use yarn in a repo with some packages in a namespaced repository requiring credentials.

[noherczeg]

I have the same problem (npm-cli works using ~/.npmrc):

$ yarn --verbose
yarn install v0.23.2
verbose 0.221 current time: 2017-04-19T03:55:32.916Z
info No lockfile found.
warning @SCOPE/APP@VERSION: No license field
[1/4] Resolving packages...
verbose 0.348 Performing "GET" request to "https://OUR_REPO/pure-uuid".
verbose 0.349 Performing "GET" request to "https://OUR_REPO/babel-core".
verbose 0.35 Performing "GET" request to "https://OUR_REPO/babel-loader".
verbose 0.35 Performing "GET" request to "https://OUR_REPO/babel-preset-es2015".
verbose 0.351 Performing "GET" request to "https://OUR_REPO/jest".
verbose 0.351 Performing "GET" request to "https://OUR_REPO/jshint".
verbose 0.352 Performing "GET" request to "https://OUR_REPO/jshint-stylish".
verbose 0.353 Performing "GET" request to "https://OUR_REPO/rimraf".
verbose 0.622 Request "https://OUR_REPO/jshint" finished with status code 401.
verbose 0.622 Performing "GET" request to "https://OUR_REPO/webpack".
verbose 0.625 Error: Couldn't find package "jshint" on the "npm" registry.
    at MessageError (/usr/share/yarn/lib/errors.js:8:5)
    at /usr/share/yarn/lib/resolvers/registries/npm-resolver.js:209:15
    at next (native)
    at step (/usr/share/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /usr/share/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13
    at process._tickCallback (internal/process/next_tick.js:103:7)
error Couldn't find package "jshint" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[vitch]

I have the same issue with the same namespaced package:

  Error: https://registry.yarnpkg.com/@glimmer/runtime/-/runtime-0.22.0.tgz: Request failed "401 Unauthorized"
      at Request.handleRequestError (/Users/kluck/.yarn/lib/fetchers/tarball-fetcher.js:231:20)
      at emitOne (events.js:96:13)
      at Request.emit (events.js:188:7)
      at Request.onRequestResponse (/Users/kluck/.yarn/node_modules/request/request.js:986:10)
      at emitOne (events.js:96:13)
      at ClientRequest.emit (events.js:188:7)
      at HTTPParser.parserOnIncomingClient (_http_client.js:474:21)
      at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      at TLSSocket.socketOnData (_http_client.js:363:20)
      at emitOne (events.js:96:13)
      at TLSSocket.emit (events.js:188:7)

I did figure out what was causing it in my case - it may or may not be the same for others...

Most projects on my machine have a local .npmrc file which points at an internal npm registry. It looks something like:

registry = http://our-registry.internal:4873

In my global ~/.npmrc I had the following:

email=me@me.com
init.author.name=Kelvin Luck
init.author.email=me@me.com
_auth=auth-token-for-internal-registry
//registry.npmjs.org/:_authToken=my-auth-for-npm-registry
@glimmer:registry=https://registry.npmjs.org/

Note that I already had to tell npm where to look for the @glimmer namespace.

The issue happened when working on a project that didn't have a local .npmrc file pointing at our registry. I guess the _auth key tries to log into npmjs.org since that is now the default registry. Hence the error.

Changing my ~/.npmrc to this solved the problem and still let me publish to our private npm registry:

email=me@me.com
init.author.name=Kelvin Luck
init.author.email=me@me.com
//our-registry.internal:4873/:_authToken=auth-token-for-internal-registry
//registry.npmjs.org/:_authToken=my-auth-for-npm-registry
@glimmer:registry=https://registry.npmjs.org/

[ErisDS]

I am still having this problem. It randomly went away of it's own accord for a while, and randomly came back.

I'm now on yarn 24.6:

yarn install v0.24.6
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
warning Pattern ["glob@latest"] is trying to unpack in the same destination "/Users/hannah/Library/Caches/Yarn/v1/npm-glob-7.1.1-805211df04faaf1c63a3600306cdf5ade50b2ec8" as pattern ["glob@7.1.1","glob@^7.0.3","glob@^7.0.5","glob@^7.1.0","glob@^7.0.4","glob@^7.0.0"]. This could result in a non deterministic behavior, skipping.
error An unexpected error occurred: "https://registry.yarnpkg.com/@glimmer/resolver/-/resolver-0.3.0.tgz: Request failed \"401 Unauthorized\"".
info If you think this is a bug, please open a bug report with the information provided in "/Users/hannah/Ghost/Ghost/core/client/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I have also seen:

error An unexpected error occurred: "https://registry.yarnpkg.com/@glimmer/di/-/di-0.1.11.tgz: Request failed \"401 Unauthorized\"".

And

error An unexpected error occurred: "https://registry.yarnpkg.com/@glimmer/node/-/node-0.22.0.tgz: Request failed \"401 Unauthorized\"".

And

error An unexpected error occurred: "https://registry.yarnpkg.com/@glimmer/compiler/-/compiler-0.22.0.tgz: Request failed \"401 Unauthorized\"".

Here's a gist of yarn-error.log

My .npmrc file looks like:

_auth="XXX="
email=github.erisds@gmail.com
//registry.npmjs.org/:_authToken=XXX

I have tried adding @glimmer:registry=https://registry.npmjs.org/ as per the previous comment to no avail.

I have tried yarn cache clear, I've changed node versions from 4 to 6, yet this problem is consistent.

What else can I try?

[ErisDS]

Found 2 related (newer 😞 ) issues:

• Getting authentication error when running yarn install #3378
• Only send authentication header for the correct registries #3407

Commenting out the auth, registry and new @Glimmer lines in my .npmrc file allowed me to get past this issue:

#_auth="XXX="
email=github.erisds@gmail.com
# //registry.npmjs.org/:_authToken=XXX
# @glimmer:registry=https://registry.npmjs.org/

There definitely appears to be a bug but it is probably best explained by #3407 if anyone is around to triage.

[vitch]

@ErisDS - Did updating the _auth line in your ~/.npmrc so that it was scoped to a specific registry not help (see my previous comment for details)?

[xdumaine]

My team has had to completely abandon scoped registries and use our private registry as a complete mirror of public, because of yarn's auth issues with scoped registries. We tried every configuration of .npmrc that we could think of, to no avail.

[xdumaine]

... and now we're back to it failing entirely.

[benedikt-roth]

Any further progress, @xdumaine? I am having the same issue and cannot find any configuration that works 😕