jakobehn / VSTSGitHubTasks

MIT License
21 stars 10 forks source link

The request was aborted: Could not create SSL/TLS secure channel. #22

Open renemadsen opened 6 years ago

renemadsen commented 6 years ago

2018-02-28T10:05:00.9817162Z ##[debug]Error when publishing release: System.AggregateException: One or more errors occurred. ---> 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.

I guess the issue is related to https://github.com/octokit/octokit.net/issues/1756 ?

playmer commented 6 years ago

We cloned the project, updated octokit (they released a patch about a week after merging the fix to the above issue), and dropped the new binaries on our agent and it seemed to fix it.

jakobehn commented 6 years ago

Updated octokit to 0.29.0 and published a new version of the task (0.11.2). Thanks for the report

renemadsen commented 6 years ago

Thanks for the update, but I don't know if this error is related:

image

If it's related to the URL being wrong, then it must be broken parameters, but I don't know how to debug these extensions.

jakobehn commented 6 years ago

Hmm, I don't see any problem with my test builds, I just reran them with the latest version of the task. Mot likely is that your GitHub repo information is not correct, giving you a 404 when trying to publish the release

renemadsen commented 6 years ago

Is it possible to get the url it's trying to do a post to?

According to https://developer.github.com/v3/repos/releases/#create-a-release it should be /repos/:owner/:repo/releases

which in this case is /repos/microting/eform-windows-service/releases

is it not going to be constructed by the fields: image

Then there is the token, but shouldn't give an 403 instead?

jakobehn commented 6 years ago

Actually, GitHub/octokit return 404 even if the token is incorrect/not valid. Just tried this. Can you try and generate a new token, maybe the token has expired?

renemadsen commented 6 years ago

I tried with a new token and still the same result. It could be great to either see the URL it's trying to post too.