Clever Geek Handbook

NuGet package - remote name could not be resolved: 'az320820.vo.msecnd.net' / The remote server returned an error: (502) Bad Gateway

I have reinstalled all operating system and Windows 7 & Windows 8 R2 Server along with VS.net 2013.

Everything works fine except for the NuGet packages (latest or download).

I am trying to solve this problem but with no success.

There are the following assumptions or problems.

  • Trial Parameters-A GET http://az320820.vo.msecnd.net/packages/castle.core.3.3.0.nupkg HTTP / 1.0 User agent: NuGet Core / 2.7.40911.287 (Microsoft Windows NT 6.1.7601 Service Pack 1) Host: az320820.vo.msecnd.net
  • An attempt to look up DNS -options-B for "az320820.vo.msecnd.net" failed. System.Net.Sockets.SocketException The requested name is valid, but no data of the requested type was found.
  • Probe parameters-C 14: 10: 46: 7695 No HTTP request received from (chrome: 480) new client socket, port 25175.14: 10: 55: 0099 nt> Warning. The ClientHello record was 508 bytes long. Some servers have problems with ClientHello larger than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 14:10: 56: 1200 No HTTP request received from (chrome: 480) new client socket, port 25176.
  • I tried changing the Options-D event , the hosts file in the \ System32 \ Driver \ etc \ hosts folder (file): 65.52.233.252 www.nuget.org
  • Tried Options-E See Attached File: Retrieving Data. See Screenshot for HTTP Requestscreenshot
+3


source to share


2 answers


I know the problem is old, but someone might be looking for it. In Windows 10: Open Network and Sharing Center, go to your Internet / Ethernet Status and click Properties.

Now go to IPv6 and click "Advanced". Go to the DNS tab.



Here, select the Add Primary and Connection-Related DNS Suffixes option and check the suffix box to add the primary DNS suffix suffix.

Fulfilling this problem.

0


source


(copied from my comment)

I'm on the nuget.org team. We no longer use "az320820.vo.msecdn.net". We are currently using "globalcdn.nuget.org" for manual download links. Usually users shouldn't have to hardcode these URLs and depend on the API endpoint: https://nuget.org/api/v2/package/Castle.Core/3.3.0

Or use the Package Content API described here: https://docs.microsoft.com/en-us/nuget/api/package-base-address-resource#download-package-content-nupkg



The latest package content API has better availability and is the preferred route these days.

If you have any problems connecting to nuget.org endpoints, please contact us at support@nuget.org.

0


source






More articles:


All Articles