Tfs Extension 2.0.39 Octo.exe cmds fail with System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.

bfiles's Avatar


05 Jan, 2018 12:04 AM

Tfs 2015 Update 3
Octopus console version 3.17.4
Using Tfs Manage Extensions I uploaded Octopus Deploy Integration extension 2.0.39 replacing old 1.2.59 version.
Installed the new extension to my collections.
Re-created the Octopus service endpoints for all Tfs Projects using the new Octopus Deploy service type.
Updated the build defs to point to the new Octopus endpoints.
But every build when run fails with this error:
2018-01-02T19:37:09.7568874Z ##[command]"E:\agent\1\tasks\OctopusCreateRelease\2.0.39\Octo.exe" create-release --project="ePortal" --releaseNumber="17.3.18002-uat09" --channel="Main-UAT" --server=https://octopus-****/aus --apiKey="********" --enableServiceMessages --releaseNotesFile="E:\agent\1\_work_aus\80\s\" --packageversion=17.3.18002-uat09
2018-01-02T19:37:09.8818951Z Octopus Deploy Command Line Tool, version 4.5.0
2018-01-02T19:38:11.1500015Z Build environment is 
2018-01-02T19:38:11.1500015Z System.Exception: Unable to connect to the Octopus Deploy server. See the inner exception for details. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
2018-01-02T19:38:11.1500015Z at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
2018-01-02T19:38:11.1500015Z at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
2018-01-02T19:38:11.1500015Z --- End of inner exception stack trace ---
2018-01-02T19:38:11.1500015Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

Seems like this is a known issue (support for tls2+) in Octo.exe tool.

So we downloaded version 4.29.0 of the Octo.exe tool and manually copied it into the task folders of each Tfs build agent. This fixed the problem and the Octopus tasks now execute successfully.

Now - my problem: How do we update the extension so that it uses a later version of Octo.exe and we do not have to continue doing this manual copying any time a new build agent is provisioned?

Thanks, Bruce.

  1. Support Staff 1 Posted by Mark Siedle on 10 Jan, 2018 06:34 AM

    Mark Siedle's Avatar

    Hi Bruce,

    Thanks for getting in touch and sorry for the late response.

    We need to update the TFS extension manually with a new version of Octo.exe as needed.

    We have published an update to the TFS and VSTS extension today (version 2.0.89) which includes Octo.exe version 4.29.0. Are you able to update to the latest extension and see if that's all working for any new build agents you provision?


  2. 2 Posted by bfiles on 12 Feb, 2018 02:25 PM

    bfiles's Avatar

    Hi Mark,
    Can you confirm that the new 2.0.89 version of the Tfs extension is compatible with Tfs 2015.3? The download page seems to indicate this version is for Tfs 2017.1 and higher, while the link to the alternative extension for Tfs 2015 still leads back to the 2.0.39 version of the extension.

  3. Support Staff 3 Posted by Mark Siedle on 13 Feb, 2018 01:16 AM

    Mark Siedle's Avatar

    Hi Bruce,

    Sorry, I mis-read your version in the initial ticket.

    The latest supported version of the TFS extension for TFS 2015 (Updates 2,3,4) is 2.0.39 and is not compatible with TFS 2015.3.

    Would it be possible for you to automate the manual copy step in TFS, so that when new agents are provisioned, the 2.0.39 version of the TFS extension is installed, then you copy the newer version of Octo.exe?


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac