"The remote name could not be resolved: 'nuget.org'"

Question

We are trying to setup CI in Visual studio environment using TFS.

Environment:

Windows 10
Microsoft Visual Studio 2017
MSVSTFS V 16.12
NuGet V 4.0

Getting below error:

https://api.nuget.org/v3/index.json: 
Unable to load the service index for source https://api.nuget.org/v3/index.json.
An error occurred while sending the request.
The remote name could not be resolved: 'api.nuget.org'

Went through many links shared in the community by the developers which were of truly great help to understand the issue.

Some of my workarounds:

http://skolima.blogspot.ru/2012/07/nuget-proxy-settings.html
- This explained about NuGet.config settings to be done
NuGet Behind Proxy
- Very resourceful stackoverflow chain, I followed the steps of creating a NuGet.config like exactly mentioned here and my config file looked of the form:

NuGet.config which I created

I am behind a company's firewall and we are trying to setup CI/CD pipeline.

In TFS: TFS Build NuGet Error

I am sure this a firewall proxy setting issue. Since I am able to access "api.nuget.org" out of the network.

Can someone suggest what is missing in NuGet.config to which i am pointing? Any other inputs free to share.

Did you mean you work properly by using the workaround in locally visual studio, but still get error info in TFS build? — PatrickLu-MSFT, Apr 16 '18 at 07:55
@PatrickLu-MSFT even in local it does not seem to pick the change. NuGet.config 'http' proxy I have added does not seem to be getting used. — abhi11, Apr 16 '18 at 13:59
Sorry for the misunderstanding, then why you say it's a workaround? How would the workaround infect your build result? Or did you just mean what you have tried for those "workarounds"? — PatrickLu-MSFT, Apr 16 '18 at 14:05
I am trying those workarounds to resolve the nuget.org firewall issue but to no result. — coder kemp, Apr 19 '18 at 18:34
What's the result if you run nuget restore command on the build agent machine manually? — Eddie Chen - MSFT, Apr 30 '18 at 02:14

score 0 · Answer 1 · answered Apr 16 '18 at 07:54

Yes, if you want to use Nuget behind Proxy, you should follow the steps in Nuget.config

Since you have post the workaround above, however still get the error info in TFS.

You should make sure you also changed the Nuget.config in your build agent/server. Win+R and enter %appdata%\nuget to get the file location.

Try to build directly through visual studio on the server instead of through TFS. This will narrow down if the issue is related to your environment or TFS side.

Moreover, you could also Verbose Output to get more detail log info for troubleshooting: Enable Verbose Debug Mode for TFS Build vNext

"The remote name could not be resolved: 'nuget.org'"

1 Answers1