Exception calling "DownloadString" with "1" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."

Hi,
Since yesterday, at least, we are getting this error when running (New-Object System.Net.WebClient).DownloadString("https://dot.net/v1/dotnet-install.ps1") > dotnet-install.ps1 or wget https://dot.net/v1/dotnet-install.ps1 from a docker container under microsoft/dotnet-framework:4.7.2-sdk, this has also been reproduced under a current Windows 10 Desktop install.

Exception calling "DownloadString" with "1" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."
At line:1 char:1
+ (New-Object System.Net.WebClient).DownloadString("https://dot.net/v1/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

Accessing from a browser works as expected.
Will this be fixed. What can we do in the meantime?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a2e484a9-5e0c-eb3e-1413-7b507c4fa07d
• Version Independent ID: 5bc7caa5-f1c2-d7d5-fe02-80c65cca9672
• Content: dotnet-install scripts
• Content Source: docs/core/tools/dotnet-install-script.md
• Product: dotnet-core
• GitHub Login: @blackdwarf
• Microsoft Alias: mairaw

[mikkelhegn]

In my experience this is because of the combination of TLS 1.2 requirement on the website and PowerShell. This explains: https://www.codyhosterman.com/2016/06/force-the-invoke-restmethod-powershell-cmdlet-to-use-tls-1-2/ And this sample above shows how to do this from PowerShell: @powershell -NoProfile -ExecutionPolicy unrestricted -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; &([scriptblock]::Create((Invoke-WebRequest -useb 'https://dot.net/v1/dotnet-install.ps1'))) <additional install-script args>"

[mikkelhegn]

Just noticed this: #5153

I see, thank you. We have used a compiled curl in the meantime. Do you think Powershell will upgrade to 1.2 as default in the following months? The dotnet-install.ps1 script in itself does not seem to fail currently.

[mairaw]

@KathleenDollard @johnbeisner can you please comment?

[KathleenDollard]

@johnbeisner Will this continue to be a problem going forward?

[mairaw]

Met with @johnbeisner today about this. There's not much we can do since this is a constraint from the environment you run the script. Hopefully the workaround to force PS to use TLS 1.2 provided by @mikkelhegn can help in this scenario.

[RajaPriyan]

In my experience this is because of the combination of TLS 1.2 requirement on the website and PowerShell. This explains: https://www.codyhosterman.com/2016/06/force-the-invoke-restmethod-powershell-cmdlet-to-use-tls-1-2/ And this sample above shows how to do this from PowerShell: @powershell -NoProfile -ExecutionPolicy unrestricted -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; &([scriptblock]::Create((Invoke-WebRequest -useb 'https://dot.net/v1/dotnet-install.ps1'))) <additional install-script args>"

Thanks ,it's working

[yehgdotnet]

Even without TLS using https, I get this error. Anyone faced the same?