How to debug 'npm ERR! 403 In most cases, you or one of your dependencies are requesting a package version that is forbidden by your security policy.'

Question

I am currently trying to set up a Jenkins and a private npm repository (Sonatype Nexus). I get the following error when I try to publish to the repository within a Jenkins build pipeline.

+ npm publish --registry https://<my-private-registry>/repository/npm-private/ npm notice  npm notice package: [email protected] npm notice === Tarball Contents ===  npm notice 2.4kB  Jenkinsfile                        ... ('notice' level info about the files) ... npm notice === Tarball Details ===  npm notice name:          ts-acoustics                             npm notice version:       0.0.0                                    npm notice package size:  13.8 kB                                  npm notice unpacked size: 47.5 kB                                  npm notice shasum:        554b6d2b41321d78e00f6a309bb61c9181a2e3d6 npm notice integrity:     sha512-QtExdu6IqZ+lH[...]r+HXolo4YCFPg== npm notice total files:   17                                       npm notice  npm ERR! code E403 npm ERR! 403 403 Forbidden - PUT https://<my-private-registry>/repository/npm-private/ts-acoustics npm ERR! 403 In most cases, you or one of your dependencies are requesting npm ERR! 403 a package version that is forbidden by your security policy. 

I find no further info about why it is forbidden in the Nexus logs and this open GitHub bug tells me that the above error text is leading in the wrong direction in most of the cases?!

Any idea of how to proceed to make publishing work?!

---

Update 1: I just saw that I have the same problem when I try to publish it manually! So Jenkins is out of the equation for simplicity reasons.

Update 2: I can do npm adduser --registry... and npm tells me

Logged in as <my-user> on https://<my-private-registry>/repository/npm-private/. 

When I do npm whoami --registry... it displays the correct user name.

When I do npm publish --registry... in the project, it shows the 403 Error

Answer 1

If you are like me and following the Node Cookbook example, or some other example where you just made your account, your error is probably like mine.

I hadn't verified my email address and got the same error (it was a new account). Once I verified, it worked (even on VPN).

Check your email and verify your account.