NuGet behind a proxy

Question

I figure out that NuGet allows proxy settings configuration since 1 4 version  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

User · Answer

Just in case you are using the https version of nuget  https   www nuget org   be aware that you have to set the values with https    https proxy https proxy user https proxy password

User · Answer

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    msecnd net

User · Answer

Try this  Basically  connection could fail if your system doesn t trust nuget certificate

User · Answer

Another flavor for same  proxy for nuget   alternatively you can set your nuget proxing settings to connect through fiddler  Below cmd will save proxy settings in in default nuget config file for user at  APPDATA  NuGet NuGet Config  nuget config -Set HTTP PROXY http   127 0 0 1 8888   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

User · Answer

Above Solution by  arcain  Plus below steps solved me the issue   Modifying the  package sources  under Nuget package manger settings to check  the checkbox to use the nuget org settings resolved my issue  I did also changed to use that nuget org  as the first choice of package source I did uncheck my company package sources to ensure the nuget was always picked  up from global sources

User · Answer

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 -  http   docs nuget org docs release-notes nuget-1 5

User · Answer

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  https   support microsoft com en-us help 4026814 windows-accessing-credential-manager

User · Answer

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      lt  xml version  1 0  encoding  utf-8   gt      lt configuration gt      lt  configuration gt    Then      nuget config -Set http proxy  http   myproxy example com 8080  -ConfigFile   Nuget Config   And finally commit your new project local Nuget config file

User · Answer

Maybe you could try this to your devenv exe config   lt system net gt       lt defaultProxy useDefaultCredentials  true  enabled  true  gt           lt proxy proxyaddress  http   proxyaddress    gt       lt  defaultProxy gt       lt settings gt           lt servicePointManager expect100Continue  false    gt           lt ipv6 enabled  true   gt       lt  settings gt   lt  system net gt    I found it from the NuGet Issue tracker  There are also other valuable comments about NuGet   network issues

User · Answer

Here s what I did to get this working with my corporate proxy that uses NTLM authentication  I downloaded NuGet exe and then ran the following commands  which I found in the comments to this discussion on CodePlex    nuget exe config -set http proxy http   my proxy address port nuget exe config -set http proxy user mydomain myUserName nuget exe config -set http proxy password mySuperSecretPassword   This put the following in my NuGet config located at  appdata  NuGet  which maps to C  Users myUserName AppData Roaming on my Windows 7 machine     lt configuration gt       lt  -- stuff -- gt       lt config gt           lt add key  http proxy  value  http   my proxy address port    gt           lt add key  http proxy user  value  mydomain myUserName    gt           lt add key  http proxy password  value  base64encodedHopefullyEncryptedPassword    gt       lt  config gt       lt  -- stuff -- gt   lt  configuration gt    Incidentally  this also fixed my issue with NuGet only working the first time I hit the package source in Visual Studio      Note that some people who have tried this approach have reported through the comments that they have been able to omit setting the http proxy password key from the command line  or delete it after-the-fact from the config file  and were still able to have NuGet function across the proxy    If you find  however  that you must specify your password in the NuGet config file  remember that you have to update the stored password in the NuGet config from the command line when you change your network login  if your proxy credentials are also your network credentials

User · Answer

The solution for me was to include    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    In the nuget config file

User · Answer

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  lt configuration gt  element     lt system net gt               lt defaultProxy useDefaultCredentials  true  gt               lt  defaultProxy gt   lt  system net gt

User · Answer

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  http   www nuget org api v2    I didn t have to change any proxy related settings

[c#] NuGet behind a proxy

Examples related to c#

Examples related to msbuild

Examples related to nuget