Install-package the underlying connection was closed

If you're using Visual Studio, first enable package restore as follows. Otherwise continue to the sections that follow. These settings can also be changed in your NuGet.

Config file; see the consent section. If your project is an older project that uses the MSBuild-integrated package restore, you may need to migrate to automatic package restore. This error occurs when you attempt to build a project that contains references to one or more NuGet packages, but those packages are not presently installed on the computer or in the project.

This situation commonly occurs when you obtain the project's source code from source control or another download. Packages are typically omitted from source control or downloads because they can be restored from package feeds like nuget.

Including them would otherwise bloat the repository or create unnecessarily large. The error can also happen if your project file contains absolute paths to package locations, and you move the project. After a successful restore, the package should be present in the global-packages folder.

The project should now build successfully. If not, file an issue on GitHub so we can follow up with you. The project. Because this file is generated dynamically through package restore, it's typically not added to source control. As a result, this error occurs when building a project with a tool such as msbuild that does not automatically restore packages. I'm not sure where it's getting the idea that a failure happened. The text was updated successfully, but these errors were encountered:.

Sorry, something went wrong. What details would you like? The command line output is here , but I wasn't able to locate a log. This machine is on a network with iPrism filtering and all websites have to be whitelisted. That log is interesting. I wish there were more detail surrounding the specifics of why it was closed.

It does seem environmental though, other folks would be reporting this issue otherwise. It may. I would have expected The underlying connection was closed: Could not establish trust relationship though. It would be so helpful if the InnerExceptions were recursively printed out. What's the best course of action for me to debug this? Filtering Wireshark for http is about all I know to without further instructions.

For debugging purposes I think this is going to be a bit harder. There should be no need to set the SecurityProtocol directly, as Chocolatey will take care of this internally. Sorry, something went wrong.

Thanks for looking into this gep Yes I can confirm that the time and date are correct. It seems to throw the same error. I have a doubt if this is related to using it through organization network, I am not very knowledgeable in network related stuff.

Adding to that for complete record, I got similar errors to install choco. I downloaded the install script, 'had' to set the below commands and only then, I was able to install choco. But they dont seem to help install packages using choco. Same issue is present on Windows Server for me when building a docker image with the same base os.

With no changes to the base image a few weeks ago i could build images normally. Can confirm that on my personal PC Windows 10 21H1 i can install packages with choco normally. I'm wondering if you have a proxy in play here, and your system isn't trusting a certificate properly through it. Thanks for the reply steviecoaster. The debug log for choco install git is already included in the very first comment under "Output Log" as a collapsible as required in the guidelines.

I can add another one for choco install git. Yes the laptop belongs to my company and runs windows 10 enterprise. Please let me know if I can provide any specifics on it. Edit: I know people using the same network and dont have any problem.

Not sure what is missing. I want to see the certificate chain Chocolatey is attempting to traverse. Sorry for the slow response steviecoaster , heres the debug log. And thanks FrdAlex , probably they are quite the same. FrdAlex Yup. I suspect that this certificate is causing issues for you:.

I'm wondering if the trace stuff only logs to console, not log files. You'll not see any output from chocolatey doing it this way. That's expected, it is streaming everything into the log file. Ah my bad, I read the output and didnt notice that its different in the file. Here is the full log, please let me know I can provide anything else. Is it on Chocolatey side? FrdAlex sbudaraj-vcc It appears to be the same certificate for both of you!

If you can get that certificate and put it in the TrustedPeople store of the machine that is failing, I expect things to begin working for you. I'll go back to our team and see if this is an "us" problem, and also check as I think we have a PowerShell script that I can link too that will help you retrieve that cert and put it in the right place automatically.

Yes please, a script would be very helpful! Hey sbudaraj-vcc and FrdAlex , this script should pull that Cisco Umbrella certificate into the TrustedPeople store of a client machine:.

Thanks steviecoaster. I ran the script, it seemed to have successfully added the certificate did it a couple of times. However, it doesnt seem to clear the problem, I seem to get the same error. It seems Cisco Umbrella is handing a different certificate each time, but all signs point to the Cisco Umbrella system being the issue. I would coordinate with whomever manages that for you.

Hello steviecoaster , that's extremely helpful. Thank you! If a different cert is handed each time, this sounds like a chocolatey issue rather than a client issue. As far as I am aware, we don't use any Cisco products.