-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL issues after running nuget locals --clear #7321
Comments
Moved to NuGet for initial investigation. |
Looks like ASP.NET Core's build hit this as well 2 days ago:
|
Related to this report as well? |
Tracking on nugetgallery repo |
@aeos how often does it happen for you? |
@aeos has full version in his first message. 2.1.302 is the SDK being used. His post lists all the runtimes and sdks installed. |
@rrelyea how does it answer which .NET Core was used with the nuget client? Why does it comment on "migrating to 2.0" then? |
I think that: means that the user ran dotnet restore with 2.1.302 --- |
Sorry for that typo. You are correct. Moving to 2.1 |
Here is how I reproduce the issue. using this simple csproj: netcoreapp2.1 Proj.Authority 1.0.0 first run |
How often does it happen? Is it 100% repro? |
It happens 100% for me and one other. It does not happen to a third. If I use a different package reference there is no errors. I use that csproj file with nothing else to replicate it however xml doesn't appear to work in comments. |
If it is 100%, then it is likely something slightly different than the intermittent thing we're chasing down. |
note that the behavior may also depend on your network e.g. do you use proxy, uplink speed and behavior, firewall setting etc. If you have 100% repro @aeos , could you provide packet capture? Also note that 2.1.403 is out. Include 2.1.5 runtime had some HTTP fixes regarding proxy and authentication. |
I believe #7314 fixes this. |
From @aeos on September 21, 2018 16:52
Steps to reproduce
We have a mono project which consists of multiple projects structured like so:
/root
/root/nuget_packages
/root/ProjectA/ProjectA.csproj
/root/ProjectB/ProjectB.csproj
/root/ProjectC/ProjectC.csproj
we build each project, pack them and push them to the /root/nuget_packages folder so that they can depend on each other. Any change we make in a dependency requires a new build/pack/push however we don't update the version number in the csproj because we are doing local development. If another project pulls a dependency, nuget cache sees the same version number and returns the cached package. To avoid this, we first run
dotnet nuget locals all --clear
. Then when we restore it gets the updated package. This might be a bad practice, there may be a better way.However, this has worked fine up until we moved to 2.0.
Expected behavior
Prior to dotnet 2.0 this worked without problems
Actual behavior
After updating to 2.0 we receive a stream of errors and a long delay before the restore completes. The errors look like this:
Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.extensions.configuration.azurekeyvault/index.json'. The SSL connection could not be established, see inner exception. Authentication failed because the remote party has closed the transport stream. Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.extensions.configuration.environmentvariables/index.json'. The SSL connection could not be established, see inner exception. Authentication failed because the remote party has closed the transport stream. Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.extensions.configuration.keyperfile/index.json'. The SSL connection could not be established, see inner exception.
Environment data
dotnet --info
output:.NET Core SDK (reflecting any global.json):
Version: 2.1.302
Commit: 9048955601
Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.302\
Host (useful for support):
Version: 2.1.2
Commit: 811c3ce6c0
.NET Core SDKs installed:
1.0.4 [C:\Program Files\dotnet\sdk]
2.0.0 [C:\Program Files\dotnet\sdk]
2.1.302 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Copied from original issue: dotnet/cli#10035
The text was updated successfully, but these errors were encountered: