npm publish has resulted in error "You need to authorize this machine using `npm adduser`" #25

furixturi · 2015-06-11T09:25:19Z

Hi,

In the 08 Publish chapter I was not able to npm publish against the .npmrc local environment. However it worked when the .npmrc file removed and with a connection to https://www.npmjs.com/. None of the following chapters worked correctly either against this local environment, and all worked well again without the .npmrc file and with a connection to https://www.npmjs.com/.

I once went through the 02 Login chapter smoothly and npm whoami returned the correct info. At this point running npm whoami also results in authentication errors.

Looking at the path that userconfig in .npmrc pointed to (userconfig = /Users/xiaoli.shen/.config/how-to-npm/npmrc), there is no such file or folder named npmrc, which might be the reason for the authentication errors.

I'm using version 2.0.0 of how-to-npm and on Mac OS 10.9.5

My npm-debug.log is as follows:

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'adduser' ]
2 info using [email protected]
3 info using [email protected]
4 verbose adduser before first PUT { _id: 'org.couchdb.user:alabebop',
4 verbose adduser   name: 'alabebop',
4 verbose adduser   password: 'XXXXX',
4 verbose adduser   email: '[email protected]',
4 verbose adduser   type: 'user',
4 verbose adduser   roles: [],
4 verbose adduser   date: '2015-06-11T09:07:53.405Z' }
5 verbose request uri http://localhost:15443/-/user/org.couchdb.user:alabebop
6 verbose request new user, so can't send auth
7 info attempt registry request try #1 at 11:07:53
8 verbose request id 8f19ff7f3662cb4c
9 http request PUT http://localhost:15443/-/user/org.couchdb.user:alabebop
10 info retry will retry, error on last attempt: Error: connect ECONNREFUSED
11 info attempt registry request try #2 at 11:08:03
12 http request PUT http://localhost:15443/-/user/org.couchdb.user:alabebop
13 info retry will retry, error on last attempt: Error: connect ECONNREFUSED
14 info attempt registry request try #3 at 11:09:03
15 http request PUT http://localhost:15443/-/user/org.couchdb.user:alabebop
16 verbose request invalidating /Users/xiaoli.shen/.npm/localhost_15443/-/user/org.couchdb.user_3Aalabebop on PUT
17 verbose adduser back [ { [Error: connect ECONNREFUSED]
17 verbose adduser     code: 'ECONNREFUSED',
17 verbose adduser     errno: 'ECONNREFUSED',
17 verbose adduser     syscall: 'connect' },
17 verbose adduser   undefined,
17 verbose adduser   undefined ]
18 verbose stack Error: connect ECONNREFUSED
18 verbose stack     at exports._errnoException (util.js:746:11)
18 verbose stack     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
19 verbose cwd /Users/xiaoli.shen/projects/nodeschool/how-to-npm
20 error Darwin 13.4.0
21 error argv "node" "/usr/local/bin/npm" "adduser"
22 error node v0.12.4
23 error npm  v2.11.1
24 error code ECONNREFUSED
25 error errno ECONNREFUSED
26 error syscall connect
27 error Error: connect ECONNREFUSED
27 error     at exports._errnoException (util.js:746:11)
27 error     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
27 error  { [Error: connect ECONNREFUSED]
27 error   code: 'ECONNREFUSED',
27 error   errno: 'ECONNREFUSED',
27 error   syscall: 'connect' }
28 error If you are behind a proxy, please make sure that the
28 error 'proxy' config is set properly.  See: 'npm help config'
29 verbose exit [ 1, true ]

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

swestcott · 2015-06-15T21:43:29Z

Ditto, same software versions and same error.

meppsilon · 2015-07-20T19:47:27Z

I'm running into this error as well. Any suggestions on how to bypass it?

smirciat · 2015-07-21T04:40:58Z

Same issue here. It sounds like @alabebop has a workaround, but I am too new to this environment to understand it. Is any further guidance available?

AnandWalvekar · 2015-07-29T10:58:25Z

It go resolved!!!

Switch to Login module (by typing "how-to-npm" on command line)
Type "npm adduser" to login
Type "npm whoami" to confirm if logged in
Switch back to the package at which you are getting error(my case it was Publish Again)
Type "npm publish"
Done

devhammer · 2015-07-31T21:40:22Z

@AnandWalvekar That workaround didn't work for me. Still fails to publish, even when npm whomi correctly returns my username.

Getting the following output:

npm ERR! publish Failed PUT 404
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "node" "C:\\Users\\USERNAME\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "publish"
npm ERR! node v0.12.5
npm ERR! npm  v2.13.3
npm ERR! code E404

npm ERR! 404 missing : @myUser/how-to-npm
npm ERR! 404
npm ERR! 404 '@myUser/how-to-npm' 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.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\USERNAME\Documents\node_code\nodeschool.io\how-to-npm\npm-debug.log

jmanuel1 · 2015-08-14T02:25:55Z

Getting same error as @devhammer, with node v0.10.35 on Windows 10.

quangnd · 2015-08-16T04:00:56Z

AnandWalvekar's solution worked with me!

davis3792 · 2015-08-21T20:58:40Z

The work around fixed it for me as well. Wasted a bunch of time getting there though.

su6a12 · 2015-08-28T17:08:57Z

Solution worked for me as well, thanks @AnandWalvekar

seonixx · 2015-08-30T14:20:19Z

Workaround worked for me. Cheers @AnandWalvekar

bennythejudge · 2015-10-03T09:33:08Z

@AnandWalvekar thanks a lot it worked but I had to bump the version.
Could a skip be provided for this step?

jondcoleman · 2015-10-03T12:29:18Z

Also had this error and workaround worked for me.

aclbros · 2015-10-18T11:15:32Z

Workaround worked for me. Cheers @AnandWalvekar

ashleygwilliams · 2015-10-21T21:23:58Z

closing in favor of #46. i believe the windows problem is already doc'd in #37

agungsantoso · 2016-03-14T08:22:17Z

AnandWalvekar's solution worked with me!

sawant · 2016-03-25T08:07:54Z

I have documented the issue and solution here #8 (comment) .

piyushdubey · 2016-03-29T20:40:27Z

@AnandWalvekar's solution worked for me as well!

lpix · 2016-03-29T20:45:30Z

@AnandWalvekar's solution worked for me! I suggest adding this as a tip in the module in case someone has the same issue

sudoVlad · 2016-06-18T04:30:36Z

@AnandWalvekar Thanks for the solution

swheatley · 2016-10-28T21:58:20Z

I had to go through the steps a few times but the work around for the solution mentioned above does work :)

sergiomgaspar · 2016-12-14T21:45:27Z

@AnandWalvekar thx for the WA.. worked like a charm :)

alundiak · 2017-12-04T18:06:21Z

@AnandWalvekar solution works for me locally. but At the moment I can't figure out why the same flow doesn't work on Jenkins.
If someone has ideas, I will very thankful.

This is cut from my custom .npmrc file created by Jenkins.

; userconfig /home/builder/.jenkins/jobs/FDD test - simple project/workspace@tmp/config3550090785588839693tmp
always-auth = true
registry = "https://my-server.com:8443/repository/my-hosted-npm"
strict-ssl = false

always-auth = true means, that I provided NPM user credentials on jenkins level, and I expected Jenkins pass/substitute creds during npm publish but I can't get why it doens't work..

renatoathaydes · 2018-01-14T20:37:50Z

Does not work!

npm adduser
Username: xxxxxx
Password:
Email: (this IS public) [email protected]
Logged in as xxxxx on https://registry.npmjs.org/.
➜  lib1 npm publish
npm ERR! code ENEEDAUTH
npm ERR! need auth auth required for publishing
npm ERR! need auth You need to authorize this machine using `npm adduser`

alundiak · 2018-01-15T21:35:05Z

@renatoathaydes

What OS u have?
what is ur .npmrc content or
what is output of npm config list?

I see, you have https://registry.npmjs.org/ as registry, so I assume npm get registry will show it. have you tried to change to http://registry.npmjs.org/ (http).

strict-ssl = false set?
Are u under/behind the some proxy/vpn?

renatoathaydes · 2018-01-16T16:22:17Z

OS: Linux renato 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

//registry.npmjs.org/:_authToken=cef314xxxxxxx
init.author.name=Renato Athaydes
init.author.email=renatoathaydes@xxxx

➜  npm config list
; cli configs
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/5.6.0 node/v9.4.0 linux x64"

; userconfig /home/renato/.npmrc
init.author.email = "renatoathaydes@xxxx"
init.author.name = "Renato Athaydes"

; node bin location = /home/renato/.nvm/versions/node/v9.4.0/bin/node
; cwd = /home/renato/programming/projects/node-lib-mismatch/lib3
; HOME = /home/renato
; "npm config ls -l" to show all defaults.

I am at home, no proxies. No strict-ssl = false that I can see. And I would prefer to not use http.

yordis · 2018-02-10T22:17:49Z

I keep getting the same error even when I successfully login. npm whoam give me the correct user but it keep failing no matter what.

JMuhire · 2018-05-14T15:37:03Z

In my ci script, I have resolved this issue using a _auth token and setting up the user email like this :

npm config set _auth $NPM_REGISTRY_TOKEN && npm config set registry $NPM_REGISTRY_URL && npm config set always-auth=true && npm config set [email protected]

petermetz · 2018-05-24T18:17:55Z

My issue was that I had the publishConfig object specified in package.json which defined an invalid URL (some private registry).
Had to set it up like this:

  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  },

zrubing · 2018-06-15T02:51:56Z

npm whoami is correct
I use sudo npm publish is failure,when i switch back to normal user then it worked

Bittttter · 2020-11-21T09:52:49Z

I just delete currentdir/.npmrc and then use nrm use to switch npm registry. And It works.

geoidesic · 2021-03-02T16:44:32Z

@Bittttter nrm use is not a thing. ?

Carnia · 2021-04-02T01:30:04Z

My issue was that I had the publishConfig object specified in package.json which defined an invalid URL (some private registry).
Had to set it up like this:
  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  },

yes, when i delete publishConfig in package.json，I can publish it normally。

TylerSustare · 2022-12-18T08:56:34Z

I had to go pro, publish the package, make the package public, and open a ticket to get my money back. It was super stupid.

zuenir · 2024-02-28T11:12:01Z

It go resolved!!!

Switch to Login module (by typing "how-to-npm" on command line)

Type "npm adduser" to login

Type "npm whoami" to confirm if logged in

Switch back to the package at which you are getting error(my case it was Publish Again)

Type "npm publish"

Done

Thank you, it helped to solve my problem

sinawic · 2024-03-27T11:54:02Z

In my ci script, I have resolved this issue using a _auth token and setting up the user email like this :

npm config set _auth $NPM_REGISTRY_TOKEN && npm config set registry $NPM_REGISTRY_URL && npm config set always-auth=true && npm config set [email protected]

@JMuhire
its 2024 and I wanna thank u for this!

i just added
registry=
_authToken=
to the .npmrc file and it workeddd

ashleygwilliams mentioned this issue Oct 21, 2015

investigate need to re-login for separate sections #46

Open

ashleygwilliams closed this as completed Oct 21, 2015

sudoVlad mentioned this issue Jun 18, 2016

How-To-NPM Publish Again freeCodeCamp/freeCodeCamp#8770

Closed

leonelsanchesdasilva added a commit to DesignLiquido/delegua-matematica that referenced this issue Sep 11, 2022

Usando publishConfig conforme workshopper/how-to-npm#25.

7033716

npm publish has resulted in error "You need to authorize this machine using npm adduser" #25

npm publish has resulted in error "You need to authorize this machine using npm adduser" #25

Comments

furixturi commented Jun 11, 2015

swestcott commented Jun 15, 2015

meppsilon commented Jul 20, 2015

smirciat commented Jul 21, 2015

AnandWalvekar commented Jul 29, 2015

devhammer commented Jul 31, 2015

jmanuel1 commented Aug 14, 2015

quangnd commented Aug 16, 2015

davis3792 commented Aug 21, 2015

su6a12 commented Aug 28, 2015

seonixx commented Aug 30, 2015

bennythejudge commented Oct 3, 2015

jondcoleman commented Oct 3, 2015

aclbros commented Oct 18, 2015

ashleygwilliams commented Oct 21, 2015

agungsantoso commented Mar 14, 2016

sawant commented Mar 25, 2016

piyushdubey commented Mar 29, 2016

lpix commented Mar 29, 2016

sudoVlad commented Jun 18, 2016

swheatley commented Oct 28, 2016

sergiomgaspar commented Dec 14, 2016

alundiak commented Dec 4, 2017 • edited Loading

renatoathaydes commented Jan 14, 2018

alundiak commented Jan 15, 2018 • edited Loading

renatoathaydes commented Jan 16, 2018

yordis commented Feb 10, 2018

JMuhire commented May 14, 2018

petermetz commented May 24, 2018

zrubing commented Jun 15, 2018

Bittttter commented Nov 21, 2020 • edited Loading

geoidesic commented Mar 2, 2021

Carnia commented Apr 2, 2021

TylerSustare commented Dec 18, 2022

zuenir commented Feb 28, 2024

sinawic commented Mar 27, 2024 • edited Loading

npm publish has resulted in error "You need to authorize this machine using `npm adduser`" #25

npm publish has resulted in error "You need to authorize this machine using `npm adduser`" #25

alundiak commented Dec 4, 2017 •

edited

Loading

alundiak commented Jan 15, 2018 •

edited

Loading

Bittttter commented Nov 21, 2020 •

edited

Loading

sinawic commented Mar 27, 2024 •

edited

Loading