NPM's nexus private server e401 E500 error handling record

use nexus Built npm Local repository , Publishing times npm ERR! code E401, The reason is that there is no basic permission , Need to log in , When logging in with your account, you will report E500 error , I checked it on the Internet , Less resources , And basically repeat , Now record the problem , For the convenience of partners with the same problems in the later stage

npm E401

npm publish  when , Details of the error are as follows ：

npm ERR! code E401
npm ERR! Unable to authenticate, need: BASIC realm="Sonatype Nexus Repository Manager"

1.npm publish

newspaper 401  BASIC realm="Sonatype Nexus Repository Manager", This is usually npm publish The employer will have this problem ,npm publish You need to have the permission of the local warehouse , Generally, it can be solved by logging in . Login use   npm login    Input nexus Users created on 、 Password and email are ok

If you can't send it after logging in , Check npm nexus Of Realms Set up , hold npm Bearer Token Reaim Put in Active in , And save

2.npm install

If it's just npm i  Words , First check the package address you use , Use nrm ls  List the current packages , It can be used nrm use  Switch

Next, check Nexus Repository Manager Upper Anonymous Whether open

npm E500

This question is strange , No similar problems were found on the Internet , Now try to write down , Not necessarily representative

home page , There is no problem with the account ,nexus Access is no problem , Namely npm login  Just when 500  了 ,

1. Confirm whether to log in   npm whoami,  View current login npm The account of ,publish You can confirm whether the user is correct when publishing the package , If you log in normally, you can end

npm whoami

2. If login is unsuccessful , newspaper E500, Homepage check nexus Whether the account password on the private server is valid , Whether the input is correct

3. Confirm no mistake , Such a rare private server as I encountered 、 All accounts are normal , Just can't log in , Continue with the following attempts

    Check the local project configuration file package.json Middle China "publishConfig" Is the address the correct private server address

4. Check local npm Default configuration item , The key is userconfig , Default address ：c:\Users\ user \.npmrc file , Save login information in the configuration file

// List npm Default configuration item for 
npm config list -l  

In my configuration, there are only the first two lines , So keep logging in E500 abnormal , Although the account information entered is correct , But still report 500, Later, the following three lines were added , namely always-auth、_auth、email After the message , It can be released normally , And directly npm whoami  View login information , Unexpectedly, the account number after successful login is displayed ,

registry=http://10.100.xx.xx:5006/repository/npm-group/
save-prefix=~
always-auth=true
_auth="dXNlcmFkbWluOnVzZXJwYXNzd29yZA=="
[email protected]

Here's an explanation ：_auth="dXNlcmFkbWluOnVzZXJwYXNzd29yZA=="// Here is [ Account number : password ] Of Base64 Encoded value , Use your own account password Base64 Replace after coding , My problem here is solved , It's ok npm publish 了 . If you have a similar problem , If it hasn't been solved here , Please continue to try to solve , If it's convenient for you , Please leave me a comment about the solution , thank you .