title: The underlying connection was closed: An unexpected error occurred on a send.--- NuGet
body: <p>Whilst trying to restore nuget packages I am getting the following:-</p>
  <blockquote>
  <p>Error 1   The underlying connection was closed: An unexpected error occurred on a send.</p>
  <p>Error 2   The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.</p>
  <p>Error 3   The command &quot;&quot;D:\root\.nuget\NuGet.exe&quot; install &quot;D:\root\packages.config&quot; -source &quot;&quot;  -NonInteractive -RequireConsent -solutionDir &quot;D:\root\&quot;&quot; exited with code 1.</p>
  <p>Error 4   Metadata file 'D:\root\project.Website.dll' could not be found  D:\root\project.UnitTests\CSC</p>
  </blockquote>
  <p>I tried the solutions provided on: <a href="https://stackoverflow.com/questions/8972497/visual-studio-2010-nuget-error-the-underlying-connection-was-closed-could-not">Visual Studio 2010 nuget error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel</a></p>
  <p>I tried the solutions provided on: <a href="https://nuget.codeplex.com/discussions/275537" rel="nofollow noreferrer">https://nuget.codeplex.com/discussions/275537</a></p>
  <p>None of them work, I was wondering if anyone else is currently having this issue? If so has anyone come up with a solution?</p>
  <p>It seemingly, may be a waiting game, for the SSL certificates to be fixed.</p>
  <p>After some further debugging with Fiddler I got the following response:</p>
  <blockquote>
  <p>fiddler.network.https&gt; HTTPS handshake to az320820.vo.msecnd.net failed. System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. &lt; An existing connection was forcibly closed by the remote host</p>
  </blockquote>
  <p>If I am correct, it seems like I am being rejected but the server, not sure why and I am hopeful this will soon resolve it self.</p>
  <p>For now I have managed to get copies of packages from other developers who hadn't cleared their package cache and continue developing this way.</p>
  <p>Someone has kindly raised the issue on code plex so hopefully we get somewhere soon: <a href="https://nuget.codeplex.com/workitem/4372" rel="nofollow noreferrer">https://nuget.codeplex.com/workitem/4372</a></p>
  <p><strong>Update</strong></p>
  <p>As of 17th November, this seems to be working again. NuGet correctly telling me it's having issues getting an older version of Ninject.Web.Common.3.2.0.0 but we have the updated edition which is fine.</p>