blocks|key|4358738|text|我也有过类似的问题。我通过在我的~/.npmrc中添加_auth解决了这个问题。请参阅doc+how+to+encode+your+nexus+credential。我使用npm+config+set+_auth+xxx添加了编码的凭据。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4358739|您将无法使用npm+config+list或npm+config+get+_auth查看该值。|4358740|entityMap|0|LINK|mutability|MUTABLE|url|https://help.sonatype.com/repomanager2/node-packaged-modules-and-npm-registries#NodePackagedModulesandnpmRegistries-EncodingCredentialsonLinux^0|G|8|R|5|2E|O|17|13|0|0|6|F|M|K|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

I had similar issue. I resolved it by adding <code>_auth</code> into my <code>~/.npmrc</code>. See the <a href="https://help.sonatype.com/repomanager2/node-packaged-modules-and-npm-registries#NodePackagedModulesandnpmRegistries-EncodingCredentialsonLinux" rel="noreferrer">doc how to encode your nexus credential</a>. I added the encoded credential using <code>npm config set _auth xxx</code>.
You wont be able to see the value using <code>npm config list</code> or <code>npm config get _auth</code>.

blocks|key|1743174|text|对我起作用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1743175|我删除了C/users/文件夹下的.npmrc文件。并运行了npx+vsts-npm-auth+-config+.npmrc命令以在用户文件夹中创建新文件|1743176|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

what worked for me is :
I deleted the .npmrc file under C/users/ folder.
and ran npx vsts-npm-auth -config .npmrc command to create a new file in the users folder

blocks|key|2246765|text|我找到了一条出路。在这个新的npm版本中，他们强制执行身份验证来访问某些包。我们意识到我们不需要对我们正在下载的任何包使用身份验证，因此我们拥有的验证码是不必要的。因此，我们只需移除它，它就能正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2246766|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I found a way out. With this new npm version they are enforcing authentication to access certain packages. We realised we don't need to use authentication for any of the packages we were downloading, hence the auth code we had was unnecessary. So we just removed it and it all worked.

blocks|key|4358704|text|当我运行一个从位于自托管Azure+DevOps+(AzDo)服务器上的非公共注册表中提取一些依赖项的npm+install时，我遇到了此错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4358705|我在项目中有一个.npmrc文件，在我的用户配置文件目录中有一个.npmrc文件，其中包含一个以前允许访问的AzDo个人访问令牌(PAT)。AzDo+UI报告我的令牌仍然有效。|4358706|PS+C:\src\app>+npm+install
npm+ERR!+code+E401
npm+ERR!+Unable+to+authenticate,+need:+Basic+realm="{INTERNAL_REGISTRY_URL}",+Negotiate,+NTLM|code-block|syntax|javascript|4358707|在我的例子中，解决方案是重新生成AzDo+PAT并更新在我的用户配置文件目录中找到的.npmrc。|4358708|entityMap^0|1F|B|0|8|6|W|6|0|0|16|6|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|P|$]]

I encountered this error when running an <code>npm install</code> that was pulling some dependencies from a non-public registry located on a self-hosted Azure DevOps (AzDo) server.
I had a <code>.npmrc</code> file in the project, and a <code>.npmrc</code> file in my user profile dir with an AzDo personal access token (PAT) that had allowed access previously. The AzDo UI reported my token as still being valid.
<pre><code>PS C:\src\app&gt; npm install
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm=&quot;{INTERNAL_REGISTRY_URL}&quot;, Negotiate, NTLM
</code></pre>
<h3>In my case, the solution was to regenerate the AzDo PAT and update the <code>.npmrc</code> found in my user profile directory.</h3>

blocks|key|2246886|text|对我来说起作用的是运行npm+login，然后输入我的用户名、密码和电子邮件来登录到.npmrc中定义的注册表。然后，我继续使用npm安装我需要的包，它起作用了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2246887|entityMap^0|B|9|16|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

What worked for me was running <code>npm login</code>, then entering my Username, Password, and Email to log in to the registry defined in <code>.npmrc</code>. I then proceeded with npm installing the packages I needed and it worked.

blocks|key|1743088|text|在我的例子中，问题是我在同一个Nexus中为npm+login命令输入了另一个注册表地址。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1743089|npm+login+--registry=http://nexus_url:port/repository/wrong_address|code-block|syntax|javascript|1743090|我的问题通过登录到正确的地址得到了解决：|1743091|npm+login+--registry=http://nexus_url:port/repository/correct_address|1743092|entityMap^0|M|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

In my case, the problem was I've entered another registry address in same Nexus for <code>npm login</code> command.
<pre><code>npm login --registry=http://nexus_url:port/repository/wrong_address
</code></pre>
My problem was solved by logging into correct address:
<pre><code>npm login --registry=http://nexus_url:port/repository/correct_address
</code></pre>

blocks|key|4358914|text|我在post中运行set的命令，并添加了“活动领域”配置文件"npm不记名令牌领域“。链接：https://help.sonatype.com/repomanager3/system-configuration/access-control/realms我的问题解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4358915|entityMap|0|LINK|mutability|MUTABLE|url|https://help.sonatype.com/repomanager3/system-configuration/access-control/realms^0|1A|29|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm run set's command from the post and add in nexus &quot;Active realms&quot; profile &quot;npm Bearer Token Realm&quot;. Links: <a href="https://help.sonatype.com/repomanager3/system-configuration/access-control/realms" rel="nofollow noreferrer">https://help.sonatype.com/repomanager3/system-configuration/access-control/realms</a>
My problem was solved.

blocks|key|1741547|text|vsts-npm-auth+-config+.npmrc+-F|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1741548|是我找到的唯一解决方案；|unstyled|1741549|编辑:确保在运行npm+install+-g+vsts-npm-auth之前|offset|length|style|CODE|1741550|entityMap^0|0|0|8|S|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|P|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|F|7|T|8|@]|9|@]|A|$]]]|N|$]]

<pre><code>vsts-npm-auth -config .npmrc -F
</code></pre>
Is the only solution I found;
Edit: make sure to run <code>npm install -g vsts-npm-auth</code> before

blocks|key|5775605|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5775606|删除了C/users/+folder下的.npmrc文件：|ordered-list-item|5775607|npm+set+registry=http....|5775608|npm+set+_auth=(|5775609|：pass+in+_auth=)：|5775610|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|M|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|N|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|O|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|P|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]]|K|$]]

<ol>
<li>Deleted the .npmrc file under C/users/ folder</li>
<li>npm set registry=http....</li>
<li>npm set _auth=(login:pass in base64):</li>
</ol>

I upgraded node version to 12.16.2 and npm version to 6.14.4. After that I am not able to run <code>npm install</code>, as I'm getting this error

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

I even tried deleting node_modules and package-lock.json and running npm install again, but doesn't change anything.

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我将node版本升级到12.16.2，将npm版本升级到6.14.4。在那之后我就不能运行npm install了，因为我得到了这个错误 code E401 npm ERR! Unable to authenticate, need: BASIC realm="Sonatype Nexus Repository Manager"我甚至尝试删除node_modules和package-lock.js

问npm错误E401:无法验证，需要: BASIC realm="Sonatype Nexus Repository Manager“
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm错误E401:无法验证，需要: BASIC realm="Sonatype Nexus Repository Manager“EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm错误E401:无法验证，需要: BASIC realm="Sonatype Nexus Repository Manager“
EN