We would like to stop supporting TLS1.0 and TLS1.1 on our Octopus Deploy server. If we stop supporting them, we get the following error during the VTST Build process on the Octopus create release step: “##[error]The underlying connection was closed: An unexpected error occurred on a send.” While the Octopus push package step is doing well.
The difference between those steps is that deploying a package will use octo.exe and releasing will use an Invoke-RestMethod in PowerShell.
Invoke-RestMethods in PowerShell by default will use TLS1.0, so that’s why we receive the error.
We used https://octopus.com/docs/api-and-integration/tfs-vsts/using-octopus-extension#UsetheTeamFoundationBuildCustomTask-AddaCreateOctopusReleaseStep to set-up the failing step.
- Octopus v2018.2.1 on Server 2012R2 with all available MS updates applied.
- Visual Studio Team Services (Online) with the Octopus Deploy Integration installed from the Visual Studio Marketplace.
- Windows 10 Pro N with all available MS updates applied as VTST Build Agent. Powershell Version: 5.1.16299.98
What is the best practice to close TLS1.0 and 1.1 on our Octopus Deploy server while keep the Create Octopus Release steps in VTST builds working?
Many thanks in advance!