blocks|key|439241|text|我可能错了，但我认为它使用的是IE的代理设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|439242|如果它看到您需要登录，它会打开一个对话框，并要求您这样做(即登录)。|439243|请在此处查看->+http://docs.nuget.org/docs/release-notes/nuget-1.5的说明|offset|length|439244|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.nuget.org/docs/release-notes/nuget-1.5^0|0|0|9|1E|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I could be wrong but I thought it used IE's proxy settings.

If it sees that you need to login it opens a dialog and asks you to do so (login that is).

Please see the description of this here -> <a href="http://docs.nuget.org/docs/release-notes/nuget-1.5" rel="noreferrer">http://docs.nuget.org/docs/release-notes/nuget-1.5</a>

blocks|key|439445|text|同样的“nuget代理”的另一种风格:你也可以设置你的nuget代理设置为通过fiddler连接。下面的命令会将代理设置保存在%25APPDATA%25\NuGet\NuGet.Config用户的默认nuget配置文件中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|439446|nuget+config+-Set+HTTP_PROXY=http://127.0.0.1:8888|code-block|syntax|javascript|439447|当你需要nuget访问互联网时，只需打开Fiddler，就会发现fiddler正在监听默认端口8888。|439448|此配置对密码更改不敏感，因为fiddler将使用上游代理为您解决任何身份验证问题。|439449|entityMap|0|LINK|mutability|MUTABLE|url|http://www.telerik.com/fiddler^0|1R|S|13|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|14|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Another flavor for same "proxy for nuget": alternatively you can set your nuget proxing settings to connect through <a href="http://www.telerik.com/fiddler" rel="noreferrer">fiddler</a>. Below cmd will save proxy settings in in default nuget config file for user at <code>%APPDATA%\NuGet\NuGet.Config</code>

<pre><code>nuget config -Set HTTP_PROXY=http://127.0.0.1:8888
</code></pre>

Whenever you need nuget to reach out the internet, just open Fiddler, asumming you have fiddler listening on default port 8888.

This configuration is not sensitive to passwork changes because fiddler will resolve any authentication with up stream proxy for you.

blocks|key|439625|text|对于任何使用VS2015的人:我遇到了一个"407+Proxy+Authentication+required“错误，这破坏了我的构建。经过几个小时的调查后，发现MSBuild在试图将Nuget作为“DownloadNuGet”目标的一部分下载时并未发送凭据。解决方案是将以下XML添加到C:\Program+Files+(x86)\MSBuild\14.0\Bin\MSBuild.exe.config的<configuration>元素中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|439626|<system.net>
++++++++++++<defaultProxy+useDefaultCredentials="true">
++++++++++++</defaultProxy>
</system.net>|code-block|syntax|javascript|439627|entityMap^0|5N|F|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

To anyone using VS2015: I was encountering a "407 Proxy Authentication required" error, which broke my build. After a few hours investigating, it turns out MSBuild wasn't sending credentials when trying to download Nuget as part of the 'DownloadNuGet' target. The solution was to add the following XML to C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe.config inside the <code>&lt;configuration&gt;</code> element: 

<pre><code>&lt;system.net&gt;
 &lt;defaultProxy useDefaultCredentials="true"&gt;
 &lt;/defaultProxy&gt;
&lt;/system.net&gt;
</code></pre>

blocks|key|654087|text|我的解决方案是包括|type|unstyled|depth|inlineStyleRanges|entityRanges|data|654088|<configuration>
++<config>
++++<add+key="http_proxy"+value="http://<IP>:<Port>"+/>
++++<add+key="http_proxy.user"+value="<user>"+/>
++++<add+key="http_proxy.password"+value="<password>"+/>
++</config>
</configuration>|code-block|syntax|javascript|654089|在nuget.config文件中。|offset|length|style|CODE|654090|entityMap^0|0|0|1|C|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The solution for me was to include 

<pre><code>&lt;configuration&gt;
 &lt;config&gt;
 &lt;add key="http_proxy" value="http://&lt;IP&gt;:&lt;Port&gt;" /&gt;
 &lt;add key="http_proxy.user" value="&lt;user&gt;" /&gt;
 &lt;add key="http_proxy.password" value="&lt;password&gt;" /&gt;
 &lt;/config&gt;
&lt;/configuration&gt;
</code></pre>

In the <code>nuget.config</code> file.

blocks|key|654151|text|也许这对其他人有帮助。对我来说，解决方案是在Visual+Studio+(2015/2017)上打开NuGet设置，并添加一个新的feed+URL：http://www.nuget.org/api/v2/。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|654152|我不需要更改任何与代理相关的设置。|654153|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nuget.org/api/v2/^0|22|S|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Maybe this helps someone else. For me the solution was to open NuGet settings on Visual Studio (2015/2017) and add a new feed URL: <a href="http://www.nuget.org/api/v2/" rel="nofollow noreferrer">http://www.nuget.org/api/v2/</a>.

I didn't have to change any proxy related settings.

blocks|key|439774|text|在Windows+Server+2016+Standard上，我只需打开凭据管理器控制面板，清除Visual+Studio缓存的不再有效的代理设置，然后重新启动Visual+Studio。下一次我打开Nuget包管理器时，系统提示我输入代理凭据，这让我再次工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|439775|请参阅：https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager|offset|length|439776|entityMap|0|LINK|mutability|MUTABLE|url|https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager^0|0|4|2D|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

On Windows Server 2016 Standard, which is what I develop on, I just had to open the Credential Manager Control Panel and clear out the cached proxy settings for Visual Studio which were no longer valid and then restart Visual Studio. The next time I opened the Nuget Package Manager I was prompted for proxy credentials, which got me working again. 

See: <a href="https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager" rel="nofollow noreferrer">https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager</a>

blocks|key|653947|text|只是一个小小的补充..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|653948|如果只需提供http_proxy设置，而不提供用户名和密码，那么我建议您将代理设置放在项目本地nuget.config文件中，并将其提交给源代码控制。这样，所有团队成员都可以获得相同的设置。|653949|创建一个空的.\nuget.config|653950|+++<?xml+version="1.0"+encoding="utf-8"?>
+++<configuration>
+++</configuration>|code-block|syntax|javascript|653951|然后：|653952|+++nuget+config+-Set+http_proxy="http://myproxy.example.com:8080"+-ConfigFile+.\Nuget.Config|653953|最后提交新项目的本地Nuget.config文件。|653954|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Just a small addition...

If it works for you to only supply the http_proxy setting and not username and password I'd recommend putting the proxy settings in a project local nuget.config file and commit it to source control. That way all team members get the same settings.

Create an empty .\nuget.config

<pre><code> &lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;configuration&gt;
 &lt;/configuration&gt;
</code></pre>

Then:

<pre><code> nuget config -Set http_proxy="http://myproxy.example.com:8080" -ConfigFile .\Nuget.Config
</code></pre>

And finally commit your new project local Nuget.config file.

blocks|key|654269|text|你好，我要进入|type|unstyled|depth|inlineStyleRanges|entityRanges|data|654270|%25appdata%25/Roaming/Nuget/NuGet.Config并删除除包源之外的每一行。这应该会给出类似这样的结果|654271|<?xml+version="1.0"+encoding="utf-8"?>
<configuration>
++<packageSources>
++++<add+key="nuget.org"+value="https://api.nuget.org/v3/index.json"+protocolVersion="3"+/>
++</packageSources>
</configuration>|code-block|syntax|javascript|654272|完整路径应为C:\Users\AppData\Roaming\NuGet\NuGet.Config|654273|基本上有一个代理集，我不知道它是如何设置的，也不知道为什么设置，但它就在那里，我也无法ping它。|654274|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Hello for me going into
%appdata%/Roaming/Nuget/NuGet.Config and removing every line except for the package sources. Which should give something like this
<pre class="lang-xml prettyprint-override"><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;configuration&gt;
 &lt;packageSources&gt;
 &lt;add key=&quot;nuget.org&quot; value=&quot;https://api.nuget.org/v3/index.json&quot; protocolVersion=&quot;3&quot; /&gt;
 &lt;/packageSources&gt;
&lt;/configuration&gt;
</code></pre>
Full path should be C:\Users&lt;username&gt;\AppData\Roaming\NuGet\NuGet.Config
Basically there was a proxy set, i don't how and why it was set but it was there and i couldn't ping it either.

blocks|key|439321|text|试试this。基本上，如果您的系统不信任nuget证书，连接可能会失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|439322|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/13747011/104344^0|2|4|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]]]]

Try <a href="https://stackoverflow.com/a/13747011/104344">this</a>. Basically, connection could fail if your system doesn't trust nuget certificate.

blocks|key|439379|text|除了@arcain的建议之外，我不得不将以下Windows+Azure内容分发网络url添加到我们的代理服务器的白名单中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|439380|.msecnd.net|code-block|syntax|javascript|439381|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Apart from the suggestions from @arcain I had to add the following Windows Azure Content Delivery Network url to our proxy server's the white-list:

<pre><code>.msecnd.net
</code></pre>

blocks|key|439803|text|作为一个迟来的回答，对我来说，这里什么都不起作用。我猜这可能取决于您公司的代理或nuget是如何实现的，但出于某种原因，我设置了以下环境变量：http_proxy和https_proxy。在我删除它们之后，nuget开始正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|439804|entityMap^0|14|5|1Z|A|2A|B|2V|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

As a late answer, for me nothing worked here. I guess this might depend on your company proxies or how the <code>nuget</code> is implemented but for some reason I had the following environment variables set: <code>http_proxy</code> and <code>https_proxy</code>. After I removed them, <code>nuget</code> started working correctly.

I figure out that NuGet allows proxy settings configuration since <a href="https://docs.microsoft.com/en-us/nuget/release-notes/nuget-1.4" rel="nofollow noreferrer">1.4 version (June 2011)</a>. But, I can't find any command line example.
I'm trying to run some build and NuGet can't connect.
How do I configure the proxy settings on the command line?

NuGet behind a proxy

我发现从开始，NuGet就允许配置代理设置。但是，我找不到任何命令行示例。我正在尝试运行一些构建，但NuGet无法连接。如何在命令行上配置代理设置？

问代理背后的NuGet
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问代理背后的NuGetEN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问代理背后的NuGet
EN