Menu
I have recently upgraded from VS2012 RC to RTM, and since the upgrade to RTM, I can no longer access nuget. I receive the following error in the Manage NuGet Packages window.
The ServicePointManager does not support proxies with the https scheme. I looked at the solution offered here in a previous stack overflow question, but it does not apply to me as I am not behind a firewall (certainly not supposed to be and verified by http://whatismyipaddress.com/proxy-check). I can also see the RSS feeds / VS can access other network resources, which in the previous question the problem was related to all VS internet traffic not just NuGet as it is in my case.
Any ideas what could have caused this, or how to restore access to NuGet? I have tried this on my machines at work, and my personal computer at home, all with the same effect.
860
From Visual Studio, select Tools > NuGet Package Manager > Package Manager Console. After the Package Manager Console pane opens, verify that the Default project drop-down list shows the project in which you want to install the package.
Visual Studio 2010 has been supported since NuGet's introduction.
In Visual Studio, select Tools, and then select Options. Select NuGet Package Manager, and then select Package Sources. Enter the feed's Name and Source URL, and then select the green (+) sign to add a new package source. If you enabled upstream sources in your feed, clear the nuget.org checkbox.
The service index location for nuget.org is https://api.nuget.org/v3/index.json .
The solution is in this answer:
Visual Studio 2010 nuget error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel
The problem is related to a bad SSL cert on the default Nuget package source.
163
I started getting this in VS2015 on one of my machines. I had an additional package feed on myget which constantly asked me for credentials and failed even when entering correct credentials. What helped me was clearing the nuget cache and config by deleting these two nuget folders:
After that I restarted Visual Studio and added my custom package source again.
30
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
