NuGet Package Manager error: The remote name could not be resolved

Question

I am using version 1.4 and getting this error:

The remote name could not be resolved: go.microsoft.com

Here are the URLs for the nuget package:

https://go.microsoft.com/fwlink/?LinkID=206669

Am i missing something here? It was working fine couple of weeks earlier.

Does that link work in the browser? – davidfowl Aug 02 '11 at 08:46 — davidfowl, Aug 02 '11 at 08:46
@dfowler - Yes.It works in the browser. – Asdfg Aug 03 '11 at 19:23 — Asdfg, Aug 03 '11 at 19:23

score 16 · Accepted Answer · answered Aug 21 '11 at 15:51

16

I had to add a new package source using the following location:

http://packages.nuget.org

Click on settings in the package manager to manage the sources.

answered Aug 21 '11 at 15:51

Peter C

2,257
2
25
28

score 5 · Answer 2 · answered Aug 26 '13 at 17:57

D'oh!... In my case, I had no internet connection on the computer. The DNS IP address was missing. So make sure you can access the internet from the computer you're trying to install the NuGet package. This is important to check specially if you're working in a Virtual Machine like I'm right now. :)

It failed with this message:

PM> Install-Package jQuery -Version 1.10.2
Install-Package : The remote name could not be resolved: 'nuget.org'
At line:1 char:1
+ Install-Package jQuery -Version 1.10.2
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Install-Package], WebException
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand

So the could not be resolved has to do with no internet connection.

"Why my Hyper-V VM using a network adaptor with only internal access can't reach nuget?" Lol — Tiramonium, Oct 03 '19 at 22:22

score 3 · Answer 3 · edited Nov 17 '16 at 14:15

3

ipconfig /flushdns at the command prompt fixed it for me.

edited Nov 17 '16 at 14:15

smottt

3,272
11
37
44

answered Nov 15 '16 at 16:27

Geoff Johnson

47
2

score 2 · Answer 4 · answered May 10 '22 at 13:38

Copy the URL (usually 'https://api.nuget.org/v3/index.json') and place it in your browser - sometimes there's an issue with the internet and the NuGet Packet Manager just can't connect to the URL.

Hope it helps for future persons having this issue.

score 0 · Answer 5 · answered May 17 '17 at 12:13

In my case, my virtual machine was able to access the internet via Chrome but not via Internet Explorer. Once I fixed the connection issues in IE (by clicking the 'Fix connection issues' button causing IE to reset the LAN adapter), NuGet was able to access the internet as well.

score 0 · Answer 6 · answered Jan 11 '19 at 18:42

I just had this problem in a virtual machine and it was perplexing given that the url worked from a browser. Updated the nuget package manager and the problem went away.

Personally, I believe it just didn't recognize the nuget repo version (v3) and gave an incorrect error message.

Naveen Kumar · Answer 7 · 2023-07-27T05:33:40.813

0

I'm Facing the same issue, While I set up my new system

http://packages.nuget.org

Go to

Tools --> NuGet Package Manager --> Package Manager settings --> Package Sources

Name: nuget.org

Source: https://api.nuget.org/v3/index.json

For Visual Studio 2022

edited Jul 27 '23 at 05:33

answered Jul 27 '23 at 05:30

Naveen Kumar

1
1

NuGet Package Manager error: The remote name could not be resolved

7 Answers7

Linked