```PS C:\> powershell -NoProfile -InputFormat N...
# general
b
Copy code
PS C:\> powershell -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient)
.DownloadString('<https://get.pulumi.com/install.ps1>'))"
Exception calling "DownloadString" with "1" argument(s): "The request was aborted: Could not create SSL/TLS secure
channel."
At line:1 char:1
any ideas? it's from an elevated prompt. it's always worked before. in a browser the cert is fine.
m
cc @bitter-oil-46081
b
Copy code
PS C:\> [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
PS C:\> powershell -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient)
.DownloadString('<https://get.pulumi.com/install.ps1>'))"
b
We recently upgraded get.pulumi.com to only support TLS 1.2, which PowerShell doesn't support out of the box by default. You can force it to use TLS 1.2 by doing
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
. We updated
<http://docs.pulumi.com|docs.pulumi.com>
to reflect this as part of our giant copy and paste command for installing on Windows.
b
also no joy
b
That is interesting.
b
hah good timing
b
What version of Windows?
b
i've had that issue before with github so just thought to try it
win10 pro whatever
"up to date" "stable"
b
Yeah, they make it hard to know these days 🙂.
b
winver says 17134.523
b
Let me boot back into my Windows 10 Pro Up To Date/Stable system and see if I can hit this as well.
b
cheers
b
I did a bunch of testing here against our staging site and it was all working for me.
b
ah
Copy code
powershell -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; iex ((New-Object System.Net.WebClient).DownloadString('<https://get.pulumi.com/install.ps1>'))"
i should read the command before i run it
doing it like that works
presumably the powershell cmd creates a new context of sorts
b
Ahh, yes.
I did not notice at first that you were invoking powershell from within powershell itself!
b
all sorted sorry for the bother
yeah i didnt think
iex needs a -tls12 switch
b
Yeah. Or maybe just support it out of the box ;-)
Sorry for the trouble, and thanks for figuring it out ;-)
b
yeah or that. .10 is noticeably quicker! worth it 😄
thanks for the help bye
b
BTW: This made me realize the message the CLI prints on windows when it is out of date doesn't include this little dance, and I opened a PR for that here: https://github.com/pulumi/pulumi/pull/2362
b
thats where i copied it from yeah. good fix
b
JFYI, we ended up just relaxing the restriction on get.pulumi.com, so it should just work out of the box with powershell again.
👍 1