Error: Could not login to npm #190

zeke · 2018-02-17T20:45:27Z

I've seen this a few times now: I run the CLI, it fails. If I run npm whoami then give npx semantic-release-cli setup another time, it works! Not sure what the deal is, as I'm not changing my login status.

First attempt fails:

$ npx semantic-release-cli setup
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? zeke
ERR! semantic-release Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (/usr/local/lib/node_modules/semantic-release-cli/src/lib/npm.js:51:21)
ERR! semantic-release     at <anonymous>
ERR! semantic-release     at process._tickCallback (internal/process/next_tick.js:188:7)
ERR! semantic-release  { Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (/usr/local/lib/node_modules/semantic-release-cli/src/lib/npm.js:51:21)
ERR! semantic-release     at <anonymous>
ERR! semantic-release     at process._tickCallback (internal/process/next_tick.js:188:7)
ERR! semantic-release   stack: 'Error: Could not login to npm.\n    at getNpmToken (/usr/local/lib/node_modules/semantic-release-cli/src/lib/npm.js:51:21)\n    at <anonymous>\n    at process._tickCallback (internal/process/next_tick.js:188:7)' }

But I'm logged in to npm:

$ npm whoami
zeke

Second attempt works:

$ npx semantic-release-cli setup
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? zeke
? What is your GitHub username? zeke

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

gr2m · 2018-02-17T20:57:57Z

Yeah I've seen that myself lately, without updating semantic-release-cli, I think. Would love it if someone could investigate

zeke · 2018-02-21T00:51:53Z

For the record, I'm still getting this error a lot.

simlu · 2018-03-03T20:32:51Z

Same here. How do you resolve this?

Edit: Nvm, just try again and again... :)

simlu · 2018-03-17T00:29:53Z

Ok, this is getting ridiculous... :/

gr2m · 2018-03-17T00:35:07Z

@simlu sorry that this frustrates you, but please be kind ❤️ we would appreciate if you could delete or edit your comment

simlu · 2018-03-17T00:51:41Z

@gr2m Apologies for not providing more details - just having a really bad day here. So this seems to be related to slow connections somehow. After tethering through my phone it worked /shrugs

cliffvick · 2018-03-29T21:45:18Z

I am still getting this error quite a bit as well. Has there been any progress on determining what is causing this?

gr2m · 2018-03-29T21:48:59Z

nope. I’m quite sure something changed on npm’s side. Nobody is looking into it right now, I get it too, all the time :( if you could look into it that’d be great

zeke · 2018-03-30T00:07:32Z

Hey @kbrandwijk and @pvdlg 👋 , I'm trying to understand how this part of the code works. Does the PUT request to CouchDB generate a new token on every request?

cli/src/lib/npm.js

Lines 24 to 27 in 45c00b4

    
           const uri = url.resolve(npm.registry, '-/user/org.couchdb.user:' + encodeURIComponent(npm.username)); 
        
           const {err, token} = await new Promise(resolve => { 
        
             client.request(uri, {method: 'PUT', body}, async (err, parsed, raw, response) => {

zeke · 2018-03-30T00:08:50Z

Wondering if we could just fall back to using the token in ~/.npmrc, using get-auth-token-from-npmrc, or something similar.

gr2m · 2018-03-30T04:59:58Z

Does the PUT request to CouchDB generate a new token on every request?

I don’t know, but looks like it? Here is how it worked before: https://github.com/semantic-release/cli/blame/bdbf616c8f0b03816f5a509e7c48d06c92a81344/src/lib/npm.js#L12 when we used npm-registry-client

I guess that would be the right code to investigate though, if there is an error, maybe log out the error entirely and see if there is anything helpful in there?

Wondering if we could just fall back to using the token in ~/.npmrc,

I think that’d be dangerous, I very often have dedicated npm accounts only for semantic-release, I woudln’t want it accidentally take a token from my personal account when I don’t want to

theoomoregbee · 2018-03-30T05:36:03Z

From working on this #185 i saw that it always generates token at first, and then complain about not able to login, trying again immediately it should work, since the first try generates the token without you knowing

check https://github.com/theo4u/cli/blob/aac04906701889d4bb17b2ae75671bb2dea012ee/src/lib/npm.js#L46
i resolved it there instead of the body because parsed returns the newly generated token

@gr2m ^^

pvdlg · 2018-03-30T05:53:00Z

The problem come from the npm registry instability. npm-registry-client include a retry mechanism that was alleviating the network/server issues.

It has been changed to handle 409 errors from some "compatible" registries in 92e15f7.

The solution would be to use a proper http client (personally I prefer https://github.com/sindresorhus/got) that would allow to use Promises, setup the authentication (token or user/pass/email) and handle the different errors. And we would need to add a retry mechanism with https://github.com/sindresorhus/p-retry.

Another solution would be to use npm-registry-client again and to promisify it with https://github.com/sindresorhus/pify so we can handle a callback with multiple arguments (err, parsed, raw and response) with multiargs.

I would rather use https://github.com/sindresorhus/got rather than continuing to deal with the multiple issues and shortcomings of npm-registry-client (we had a bunch of problems with it in https://github.com/semantic-release/npm).

timiscoding · 2018-04-04T01:50:31Z

I'm new to semantic-release-cli and I sometimes get this issue. First time I ran setup it logged in fine but subsequent attempts kept failing then after a while, it seemed to work again. Here are my logs running the module with npm_config_loglevel=verbose:

login failure

request uri https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding
verb semantic-release request new user, so can't send auth
info semantic-release attempt registry request try #1 at 10:48:28
verb semantic-release request id 4733ce8b8e603591
http semantic-release request PUT https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding
http semantic-release 201 'https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding'
verb semantic-release headers { 'content-type': 'application/json',
verb semantic-release   'content-encoding': 'gzip',
verb semantic-release   'cache-control': 'max-age=300',
verb semantic-release   'transfer-encoding': 'chunked',
verb semantic-release   'accept-ranges': 'bytes',
verb semantic-release   date: 'Wed, 04 Apr 2018 00:48:29 GMT',
verb semantic-release   via: '1.1 varnish',
verb semantic-release   connection: 'keep-alive',
verb semantic-release   'x-served-by': 'cache-syd18921-SYD',
verb semantic-release   'x-cache': 'MISS',
verb semantic-release   'x-cache-hits': '0',
verb semantic-release   'x-timer': 'S1522802908.204149,VS0,VE1702',
verb semantic-release   vary: 'Accept-Encoding, Accept' }
ERR! semantic-release Error: Could not login to npm.

login success

request uri https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding
verb semantic-release request new user, so can't send auth
info semantic-release attempt registry request try #1 at 10:50:30
verb semantic-release request id 393737a7265f2531
http semantic-release request PUT https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding
http semantic-release 201 'https://registry.npmjs.org/-/user/org.couchdb.user:timiscoding'
verb semantic-release headers { 'content-type': 'application/json',
verb semantic-release   'cache-control': 'max-age=300',
verb semantic-release   'content-length': '127',
verb semantic-release   'accept-ranges': 'bytes',
verb semantic-release   date: 'Wed, 04 Apr 2018 00:50:32 GMT',
verb semantic-release   via: '1.1 varnish',
verb semantic-release   connection: 'keep-alive',
verb semantic-release   'x-served-by': 'cache-syd18935-SYD',
verb semantic-release   'x-cache': 'MISS',
verb semantic-release   'x-cache-hits': '0',
verb semantic-release   'x-timer': 'S1522803031.714634,VS0,VE1682',
verb semantic-release   vary: 'Accept-Encoding, Accept' }
info semantic-release Successfully created npm token.

It appears that on the first try, the response is sending back json data but on subsequent tries, it sends back compressed data and so the code @zeke linked is not extracting the token.

Update: Replacing

cli/src/lib/npm.js

Line 45 in 45c00b4

resolve(response.body);

with

if (response.headers['content-encoding'] === 'gzip') {
    zlib.gunzip(response.body, (err, buffer) => {
      if (err) reject(err);
      resolve(JSON.parse(buffer.toString('utf8')));
    })
  } else {
    resolve(response.body);
  }
}

seems to have fixed my issue.

PSanetra · 2018-04-06T16:36:50Z

I have created the PR #199, which will probably fix this issue. I did not receive the error message "Error: Could not login to npm", but "Invalid authentication code" since I am using 2FA.

selbekk · 2018-04-08T17:43:28Z

Had the same problem, but resolved itself after running npm whoami as suggested.

semantic-release-bot · 2018-04-09T18:29:10Z

🎉 This issue has been resolved in version 3.6.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

pvdlg · 2018-04-09T18:29:50Z

This should be fixed in 3.6.5. Please let us know if the issue is indeed fixed.

zeke · 2018-04-09T19:37:12Z

Thanks, @pvdlg! 🙏

richardschneider · 2018-06-20T13:41:13Z

@pvdlg I'm running 4.0.5 and still get the error!

> npm whoami
makaretu

> semantic-release-cli -v
4.0.5

> semantic-release-cli setup
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? makaretu
ERR! semantic-release Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (C:/Users/Owner/AppData/Roaming/npm/node_modules/semantic-release-cli/src/lib/npm.js:55:21)
ERR! semantic-release     at <anonymous>
ERR! semantic-release     at process._tickCallback (internal/process/next_tick.js:188:7)
ERR! semantic-release  { Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (C:/Users/Owner/AppData/Roaming/npm/node_modules/semantic-release-cli/src/lib/npm.js:55:21)
ERR! semantic-release     at <anonymous>
ERR! semantic-release     at process._tickCallback (internal/process/next_tick.js:188:7)
ERR! semantic-release   stack: 'Error: Could not login to npm.\n    at getNpmToken (C:/Users/Owner/AppData/Roaming/npm/node_modules/semantic-release-cli/src/lib/npm.js:55:21)\n    at <anonymous>\n    at process._tickCallback (internal/process/next_tick.js:188:7)' }

simlu · 2018-06-20T14:31:14Z

@richardschneider does this happen constantly or just occasionally? If it happens evey time I'd say it's a different issue (credentials to incorrect etc)

RemeJuan · 2018-09-03T06:09:01Z

I just ran into this myself on 4.0.7 and I got around it by turning off 2fa on npm, which is not ideal.

Seem maybe SR cli does not understand the 2fa with NPM, but it asked for it with guthub.

kariae · 2018-09-21T20:12:18Z

I confirm that the issue still exists on 4.0.7 even though npm whoami gives the good username

EDIT: after a quick debugging, I don't get E401 as code.error as supposed in npm.js#L35

for me, it's EOTP as code error, please someone confirm, I can send a PR for that ;)

lgaticaq · 2018-09-21T22:49:17Z

Some code error EOTP with version 4.0.7

gr2m · 2018-09-24T20:21:06Z

did that get resolved via #238?

jimthedev · 2018-10-01T14:24:29Z

Hey all, just a heads up that if you are still having this issue or something resembling this issue on OSX then make sure to check that an outdated isn't saved in your OSX keychain. I'd reset my bot account via the npm web interface but didn't do the same in my osx keychain which had my old password. You can check this by going to Keychain Access > All Items then search for semantic-release-cli:npm. Hope it helps someone who thinks they have this issue but actually have other problems. :)

isthatcentered · 2019-04-05T05:05:20Z

If you run your command with yarn ..., try running it with npm .... This "solves" the issue for me.

(I know this issue is closed but it comes up in the first results in google so adding this solution seems useful)

Jeff-Tian · 2020-05-18T10:27:13Z

I met the error today, finally figured out that the username should be all in lowercase.

npx semantic-release-cli setup                                                                                 $(spaceship_rprompt)
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? Jeff-Tian
? What is your npm password? [hidden]
ERR! semantic-release Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (/Users/tianjef/.npm/_npx/17020/lib/node_modules/semantic-release-cli/src/lib/npm.js:25:21)
ERR! semantic-release     at processTicksAndRejections (internal/process/task_queues.js:97:5)
ERR! semantic-release  Error: Could not login to npm.
ERR! semantic-release     at getNpmToken (/Users/tianjef/.npm/_npx/17020/lib/node_modules/semantic-release-cli/src/lib/npm.js:25:21)
ERR! semantic-release     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
ERR! semantic-release   stack: 'Error: Could not login to npm.\n' +
ERR! semantic-release     '    at getNpmToken (/Users/tianjef/.npm/_npx/17020/lib/node_modules/semantic-release-cli/src/lib/npm.js:25:21)\n' +
ERR! semantic-release     '    at processTicksAndRejections (internal/process/task_queues.js:97:5)'
ERR! semantic-release }

wechat-api on  master [!] is 📦 v0.0.0-development via ⬢ v12.16.2 at ☸️  kubesail-jeff-tian (jeff-tian) took 36s
➜ npm whoami
jeff-tian

wechat-api on  master [!] is 📦 v0.0.0-development via ⬢ v12.16.2 at ☸️  kubesail-jeff-tian (jeff-tian)
➜ npx semantic-release-cli setup
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? jeff-tian
? What is your npm password? [hidden]
? What is your GitHub username? jeff-tian

gr2m · 2020-05-18T18:03:44Z

could you send a pull request that lower-cases the username?

Co-authored-by: Jeff Tian <[email protected]>

pvdlg added the cli label Feb 18, 2018

gr2m mentioned this issue Mar 31, 2018

Add option to recreate local password key chain #186

Open

pvdlg mentioned this issue Apr 6, 2018

Unable to login to npm semantic-release/semantic-release#732

Closed

PSanetra mentioned this issue Apr 6, 2018

fix(npm): use parsed body in case response.body is gzip encoded #199

Closed

pvdlg mentioned this issue Apr 7, 2018

Fix "Could not login to npm" error #200

Merged

pvdlg closed this as completed in #200 Apr 9, 2018

lgaticaq mentioned this issue Sep 24, 2018

fix(npm): fix capture otp error #238

Merged

Jeff-Tian pushed a commit to Jeff-Tian/cli that referenced this issue May 19, 2020

fix: lower-case the npm username (semantic-release#190)

71b1f0a

gr2m pushed a commit that referenced this issue May 19, 2020

fix: lower-case the npm username (#190) (#341)

3c5146d

Co-authored-by: Jeff Tian <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Could not login to npm #190

Error: Could not login to npm #190

zeke commented Feb 17, 2018

gr2m commented Feb 17, 2018

zeke commented Feb 21, 2018

simlu commented Mar 3, 2018 •

edited

Loading

simlu commented Mar 17, 2018

gr2m commented Mar 17, 2018 •

edited

Loading

simlu commented Mar 17, 2018

cliffvick commented Mar 29, 2018

gr2m commented Mar 29, 2018

zeke commented Mar 30, 2018

zeke commented Mar 30, 2018

gr2m commented Mar 30, 2018

theoomoregbee commented Mar 30, 2018 •

edited

Loading

pvdlg commented Mar 30, 2018

timiscoding commented Apr 4, 2018 •

edited

Loading

PSanetra commented Apr 6, 2018

selbekk commented Apr 8, 2018

semantic-release-bot commented Apr 9, 2018

pvdlg commented Apr 9, 2018

zeke commented Apr 9, 2018

richardschneider commented Jun 20, 2018

simlu commented Jun 20, 2018 •

edited

Loading

RemeJuan commented Sep 3, 2018

kariae commented Sep 21, 2018 •

edited

Loading

lgaticaq commented Sep 21, 2018

gr2m commented Sep 24, 2018

jimthedev commented Oct 1, 2018

isthatcentered commented Apr 5, 2019 •

edited

Loading

Jeff-Tian commented May 18, 2020

gr2m commented May 18, 2020

Error: Could not login to npm #190

Error: Could not login to npm #190

Comments

zeke commented Feb 17, 2018

gr2m commented Feb 17, 2018

zeke commented Feb 21, 2018

simlu commented Mar 3, 2018 • edited Loading

simlu commented Mar 17, 2018

gr2m commented Mar 17, 2018 • edited Loading

simlu commented Mar 17, 2018

cliffvick commented Mar 29, 2018

gr2m commented Mar 29, 2018

zeke commented Mar 30, 2018

zeke commented Mar 30, 2018

gr2m commented Mar 30, 2018

theoomoregbee commented Mar 30, 2018 • edited Loading

pvdlg commented Mar 30, 2018

timiscoding commented Apr 4, 2018 • edited Loading

PSanetra commented Apr 6, 2018

selbekk commented Apr 8, 2018

semantic-release-bot commented Apr 9, 2018

pvdlg commented Apr 9, 2018

zeke commented Apr 9, 2018

richardschneider commented Jun 20, 2018

simlu commented Jun 20, 2018 • edited Loading

RemeJuan commented Sep 3, 2018

kariae commented Sep 21, 2018 • edited Loading

lgaticaq commented Sep 21, 2018

gr2m commented Sep 24, 2018

jimthedev commented Oct 1, 2018

isthatcentered commented Apr 5, 2019 • edited Loading

Jeff-Tian commented May 18, 2020

gr2m commented May 18, 2020

simlu commented Mar 3, 2018 •

edited

Loading

gr2m commented Mar 17, 2018 •

edited

Loading

theoomoregbee commented Mar 30, 2018 •

edited

Loading

timiscoding commented Apr 4, 2018 •

edited

Loading

simlu commented Jun 20, 2018 •

edited

Loading

kariae commented Sep 21, 2018 •

edited

Loading

isthatcentered commented Apr 5, 2019 •

edited

Loading