Visual Studio 2010 nuget error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel

Question

Whenever I'm trying to install something or even just list the packages I get this error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel"

I tried this solution from Codeplex with no luck.

I use the latest version of Nuget.

I also tried different options in devenv.exe.config like this:

<servicePointManager  checkCertificateName="false"    checkCertificateRevocationList="false"/>

score 96 · Accepted Answer · edited Feb 29 '16 at 15:07

96

Go to VS2010 → Tools → Library Package Manager → Package Manager Settings.
Choose Package Manager → Package Sources.
Add a new package source as:
- Name: NugetSource
- Source: http://packages.nuget.org/v1/FeedService.svc/
Move Up the newly added package source to first position.
UnCheck existing "Nuget official package source"
Restart VS2010.

edited Feb 29 '16 at 15:07

Wai Ha Lee

8,598
83
57
92

answered Feb 27 '12 at 09:25

Sunil

2,885
5
34
41

3

Thank you, It also worked for me, on Visual Studio 2013 Express, behind corporate proxy/firewall. Just wanted to add, that It didn't required me to Restart Visual studio either. It will just work. – Saad Farooq Nov 03 '14 at 05:32

score 22 · Answer 2 · answered Dec 06 '12 at 15:33

22

Go to https://nuget.org/ and get its certificate.

For example, if you're using Firefox: after opening nuget site - click site's icon on the left side of address bar, click 'More Information', and on the Security tab there should be 'Web-site identity' section with 'View certificate' button. Click there, in the opened dialog select Details tab - there you should see chain for *.nuget.org. Click button 'Export' at the bottom and save certificate to the file (add .cer extension manually, because dialog won't do it for you).

Now you need to setup you system so that it will trust the certificate. Press Win+R (Run dialog will be opened) -> type mmc there and run it (with admin privileges if you have UAC turned on). There select File -> Add or remove snapin... -> select Certificates on the left, in the dialog select Computer account and Local computer. Click OK - the tree will have Certificates node in the Console root. Open it and file folder Trusted People. From its context menu select All tasks -> Import... -> Select file that you have exported before and import it.

Everything should be working fine.

answered Dec 06 '12 at 15:33

Ivan Danilov

14,287
6
48
66

1

In the browser I don't se the sertificate errors now, but my VS still could not install the package. – Akim Khalilov Dec 10 '12 at 13:02
@Akim I don't have errors either, but I've been seeing the same error until I added nuget certificate to TrustedPeople. Probably it is not required for establishing connection and viewing site contents, but required to install binaries from the site to your box. – Ivan Danilov Dec 10 '12 at 17:59
2

For two days, I've been looking for the cause and tried everything. Finally, your solution is the only one that works on my VS 2019. Thank you. – Adel Sal Nov 11 '19 at 18:43
The only thing that worked for me on VS 2017 – Jorge Urreta Apr 28 '21 at 12:21
This worked in VS 2022 too for me, thanks! – eggsloveoats Oct 28 '22 at 04:06
This did not work for me. – Milton May 26 '23 at 16:36

score 12 · Answer 3 · answered Jul 22 '13 at 15:12

12

We had the same issue in work, and we resolved this by dropping the secure socket, Https -> http. This means you can use the V2 URL http://nuget.org/api/v2/.

Possibly an issue getting rid of the secure socket, but the above URL (http://packages.nuget.org/v1/FeedService.svc/) is also unsecure.

answered Jul 22 '13 at 15:12

Christian Phillips

18,399
8
53
82

When I try that, I get a http 404. – guiomie Mar 10 '14 at 18:56
Which URL are you trying? the first? I just tried that one and it's working fine – Christian Phillips Mar 10 '14 at 21:29

score 8 · Answer 4 · answered Jun 01 '12 at 06:58

8

There's apparently an issue with the SSL cert on go.microsoft.com. Change the package source url to http://packages.nuget.org/v1/FeedService.svc/ and it should work just fine.

answered Jun 01 '12 at 06:58

anand

81
1
1

score 8 · Answer 5 · answered May 07 '14 at 10:19

8

Related: ServicePointManager does not support proxies with the https scheme

If you've previously had Fiddler open, you might well have a certificate for nuget.org that is invalid.

If so, open up MMC, add the Certificates snapin (current User) and remove nuget.org from the Personal store.

Example certificate to remove

Due to Nuget keeping a handle to this cert (seemingly) you will have to restart Visual Studio. Afterwards, you should have a good time.

answered May 07 '14 at 10:19

AndyElastacloud

625
5
21

2

Thanks. it is certmgr.msc by the way. – Teoman shipahi Jan 02 '15 at 19:34
2

This fixed it for me, although the cert wasn't named nuget.org, deleted all with nuget and myget in the name though. Many thanks for posting your finding Andy – Janaka Jun 11 '15 at 08:59

score 4 · Answer 6 · edited Jul 22 '14 at 07:17

4

Go to VS2012 -> Tools -> Library Package Manager -> Package Manager Settings Choose Package Manager -> Package Sources.

Add a new package source as: Name= NugetSource Source= http://packages.nuget.org/v1/FeedService.svc/
Move Up the newly added package source to first position.
UnCheck existing "Nuget official package source"
Restart VS2012.

This is working on my machine.

edited Jul 22 '14 at 07:17

Paresh Mayani

127,700
71
241
295

answered Jul 22 '14 at 07:07

chandan

69
2

score 3 · Answer 7 · answered Nov 26 '20 at 21:56

If nothing from above works, try this....

Try pasting the following into a .reg file and run it. Then try running your NuGet command (no reboot required).

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

Ran into this issue because TLS1.2 was not enabled (similar to Tony's response). Using http does not fix the situation because NuGet redirects to https now that TLS1.2 is enforced.

thanks to "neoscribe"

score 2 · Answer 8 · answered Jan 21 '15 at 22:00

2

As of today 21-Jan-2015, the correct url is https://www.nuget.org/api/v2/. The www is required or the certificate fails. Do NOT fall back to http because you are opening your code and all of its consumers to a nasty MITM vector.

answered Jan 21 '15 at 22:00

psaxton

1,693
19
24

This also worked for me apart from that FeedService url. – T Gupta Aug 17 '15 at 08:11

score 1 · Answer 9 · answered Mar 30 '18 at 08:36

1

For me the problem was solved by clearing the nuget cache (and restarting VS)

answered Mar 30 '18 at 08:36

JBSnorro

6,048
3
41
62

score 0 · Answer 10 · edited Aug 18 '15 at 15:54

0

I could solve this problem by dropping the secure socket, https -> http. Go to Tools -> Nuget Package Manager -> Package Sources, then add a new source, but without https:

This means http://nuget.org/api/v2/.

edited Aug 18 '15 at 15:54

user3666197

1
6
50
92

answered Aug 18 '15 at 15:30

Vladimir

1

score 0 · Answer 11 · answered Sep 29 '15 at 16:23

0

I had to remove https in Local machine settings for Nuget and added (http) it to user level in Tools -> Library Package Manager -> Package Manager Settings Choose Package Manager -> Package Sources.

answered Sep 29 '15 at 16:23

jay

1

score 0 · Answer 12 · answered Jan 17 '21 at 22:18

0

i have had no luck with any method related to Visual Studio. Not updating everything, not manually adding the Root Certificate of https://api.nuget.org/v3/index.json to windows, etc. How I fixed it:

nuget restore MySolution.sln

Download nuget here.

answered Jan 17 '21 at 22:18

kellogs

2,837
3
38
51

Visual Studio 2010 nuget error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel

12 Answers12

Linked