Restore fails with "An error occurred while sending the request." for some packages

atanasa commented 8 years ago

Restore of the package "NETStandard.Library" (and others) fails with:

error: Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/netstandard.library/1.0.0-rc2-23811/netstandard.library.1.0.0-rc2-23811.nupkg'.
error: An error occurred while sending the request.
error:   A connection with the server could not be established
error: Unable to load package 'NETStandard.Library'.
trace: System.AggregateException: One or more errors occurred. (Unable to load package 'NETStandard.Library'.) ---> 
NuGet.Protocol.Core.Types.FatalProtocolException: Unable to load package 'NETStandard.Library'.
trace:    at NuGet.Protocol.Core.v3.RemoteRepositories.PackageUtilities.<OpenNuspecFromNupkgAsync>d__0.MoveNext()

I think all packages on myget fail with this error (or maybe rc2 packages).

The dependency is defined as:

    "dependencies": {
        "NETStandard.Library": "1.0.0-rc2-23811"
    }

Version of dotnet cli: 1.0.0-beta-001494

Steps to reproduce:

Create empty folder
Run there "dotnet new"
Run there "dotnet restore -v=debug > log.txt"

Using a browser to download the file 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/netstandard.library/1.0.0-rc2- 23811/netstandard.library.1.0.0-rc2-23811.nupkg' succeeds.

Full log: log.txt

blackdwarf commented 8 years ago

@atanasa which OS?

atanasa commented 8 years ago

Windows 7 64-bit

blackdwarf commented 8 years ago

@atanasa interesting enough, I cannot repro exactly this, but on my Win7 SP1 box with the latest rel/1.0.0 build 1.0.0-beta-001504 dotnet restore fails with HTTP timeout exceptions. Can you try the latest and see what is the result on your end? Thanks!

atanasa commented 8 years ago

It has something to do with my proxy settings for the WinINET stack (i.e. the Internet Options proxy). If I turn off the proxy, it works. If I run Fiddler (that sets a different proxy), the error is "security error" even though the fiddler certificate is trusted by windows. It is strange that if I have the proxy on, I can download the package using the browser. It could be my corporate proxy filtering out strange http clients, though it is strange that Fiddler would also break the connection.

I have a workaround for my case.

blackdwarf commented 8 years ago

@atanasa to me it didn't repro on a Win10 machine with newest CLI. Will try on Win7 again and if it doesn't repro there will close the issue. This OK with you?

blackdwarf commented 8 years ago

Well, a restore problem reproed for me with the latest bits on my Win7 SP1 machine.

Steps to reproduce

Install latest bits
Open up PowerShell
mkdir new followed by cd new
dotnet new
dotnet restore

Expected behavior

The restore operation succeeds and lock file is written.

Actual behavior

The restore operation is extremely slow and never completes. The console is filled with these errors:

.0.0-rc2-23811.nupkg
log  : Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.globalization
/4.0.11-rc2-23811/system.globalization.4.0.11-rc2-23811.nupkg'.
log  : The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.globalization/4.0.11-
rc2-23811/system.globalization.4.0.11-rc2-23811.nupkg' has timed out after 100000ms.
info :   GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.globalization/4.0.11-rc2-23811/system.gl
obalization.4.0.11-rc2-23811.nupkg
log  : Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem
/4.0.1-rc2-23811/system.io.filesystem.4.0.1-rc2-23811.nupkg'.
log  : The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem/4.0.1-r
c2-23811/system.io.filesystem.4.0.1-rc2-23811.nupkg' has timed out after 100000ms.
info :   GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem/4.0.1-rc2-23811/system.io.
filesystem.4.0.1-rc2-23811.nupkg
log  : Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io/4.1.0-rc2-
23811/system.io.4.1.0-rc2-23811.nupkg'.
log  : The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io/4.1.0-rc2-23811/sy
stem.io.4.1.0-rc2-23811.nupkg' has timed out after 100000ms.
info :   GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io/4.1.0-rc2-23811/system.io.4.1.0-rc2-2
3811.nupkg
log  : Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.net.sockets/4
.1.0-rc2-23811/system.net.sockets.4.1.0-rc2-23811.nupkg'.
log  : The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.net.sockets/4.1.0-rc2
-23811/system.net.sockets.4.1.0-rc2-23811.nupkg' has timed out after 100000ms.
info :   GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.net.sockets/4.1.0-rc2-23811/system.net.s
ockets.4.1.0-rc2-23811.nupkg
log  : Failed to download package from 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem
.primitives/4.0.1-rc2-23811/system.io.filesystem.primitives.4.0.1-rc2-23811.nupkg'.
log  : The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem.primiti
ves/4.0.1-rc2-23811/system.io.filesystem.primitives.4.0.1-rc2-23811.nupkg' has timed out after 100000ms.
info :   GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.io.filesystem.primitives/4.0.1-rc2-23811
/system.io.filesystem.primitives.4.0.1-rc2-23811.nupkg
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.runtime/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.runtime/index.json' h
as timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.reflection.primitives/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.reflection.primitives
/index.json' has timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.reflection.typeextensions/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.reflection.typeextens
ions/index.json' has timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.reflection/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.reflection/index.json
' has timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://api.nuget.org/v3-flatcontainer/system.runtime/index.js
on'.
error: The HTTP request to 'GET https://api.nuget.org/v3-flatcontainer/system.runtime/index.json' has timed out after 10
0000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.net.primitives/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.net.primitives/index.
json' has timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.reflection.extensions/index.json'.
error: The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.reflection.extensions
/index.json' has timed out after 100000ms.
error: Failed to retrieve information from remote source 'https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/sy
stem.runtime/index.json'.
error:   The HTTP request to 'GET https://dotnet.myget.org/F/dotnet-core/api/v3/flatcontainer/system.runtime/index.json'
 has timed out after 100000ms.

My env

.NET Command Line Tools (1.0.0-beta-001540)

Product Information:
 Version:     1.0.0-beta-001540
 Commit Sha:  6aeed1f52d

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.1.7601
 OS Platform: Windows
 Runtime Id:  win7-x64

/cc @piotrpMSFT

RobTheX commented 8 years ago

Hello,

I am new at .NET Core and facing a similar problem when trying to restore my first test project. I am behind a proxy, however, it seems that some packages can be downloaded successfully, some not (see listing extract below).

I also use Windows 7 64bit, so I guess that is the same bug as described above, isn't it?

If I try to run the project after restoring in spite of the error messages, it fails with:

F:\Temp\hwapp>dotnet run Can not find runtime target for framework 'DNXCore,Version=v5.0' and RID's 'win7-x64'. Possible causes:

Project is not restored or restore failed - run dotnet restore
Project is not targeting runable framework (netstandardapp* or net*)

F:\Temp\hwapp>dotnet run Can not find runtime target for framework 'DNXCore,Version=v5.0' and RID's 'win7-x64'. Possible causes:

Project is not restored or restore failed - run dotnet restore
Project is not targeting runable framework (netstandardapp* or net*)

Restoring messages (extract):

F:\Temp\hwapp>dotnet restore

[.....]

F:\Temp\hwapp>dotnet run Can not find runtime target for framework 'DNXCore,Version=v5.0' and RID's 'win7-x64'. Possible causes:

Project is not restored or restore failed - run dotnet restore
Project is not targeting runable framework (netstandardapp* or net*)

F:\Temp\hwapp>dotnet run Can not find runtime target for framework 'DNXCore,Version=v5.0' and RID's 'win7-x64'. Possible causes:

Project is not restored or restore failed - run dotnet restore
Project is not targeting runable framework (netstandardapp* or net*)

F:\Temp\hwapp>

RobTheX commented 8 years ago

... ok, I found the solution for my problem: I removed/commented the "clear" statement in the "NuGet.Config" file in my project directory (see screenshot). Then restoring worked (I still had some "Not Found .." messages though) and I could also run the project.

capture

kierenj commented 8 years ago

I have similar errors, but only intermittently, and only when running dotnet restore under a Docker for Windows container. The same URLs which fail with "Couldn't connect to the server" then work perfectly when I copy-paste them into the Windows host browser. Note, I don't have a <clear/> in my NuGet.config. In my last attempt, all failed URLs were for the host dotnetmyget.blob.core.windows.net.

I just added a <clear/> clause to NuGet.config and the NuGet official feed to the bottom of the list - still loads of errors, but a mix of timeouts, DNS errors, "server returned nothing" errors and "couldn't connect to server" errors...

blackdwarf commented 8 years ago

@kierenj which Windows version are you using?

kierenj commented 8 years ago

@blackdwarf Win10 64-bit. Really confusing since it did work once or twice a few days ago, and it's still intermittent. Not sure what I can do to diagnose it! Could be an issue with my machine, or Docker, or something dotnetty... any tips greatly appreciated

blackdwarf commented 8 years ago

@kierenj I encountered the same problem, but on Win7 SP1 and the problem was in the virtual adapters on the machine (e.g. Virtual Box networking adapter, though it repro-ed with VMWare installed as well). I haven't played with Docker on Windows (yet 😄 ) but could it be something similar?

kierenj commented 8 years ago

@blackdwarf / others ... I fixed this by going into Docker for Windows' settings, then Network, then un-checking 'VPN compatibility mode', which is ON by default.

livarcocc commented 7 years ago

If you guys run into something like this again, please open a new issue under the NuGet repo.

dotnet / sdk