UserPerson3000Hey there, our servers recently require TLS 1.2 so we started getting an error when calling wyUpdate.exe "Error trying to save file: Error downloading "https://sitenamehere.com/wyserver.zip": The underlying connection was closed: An unexpected error occurred on a send."
After browsing through the forums I see a lot of "we do support tls1.2 just use .net40 when building wyupdate.exe" which we do and I still get that error. I found a solution here: https://stackoverflow.com/questions/4137106/are-there-net-implementation-of-tls-1-2/32892997#32892997 which entails changing registry key. This worked but not the route we want to go.
The other solution was to pull down the opensource project and add the line of code suggested here: https://wyday.com/forum/t/3882/error-downloading-could-not-create-ssltls-secure-channel/#post-18616 . This also works and we don't mind doing this, but leads me to a couple of questions: 1. Are these the only two options, or do you know of another?2. Is this the correct, up to date repo: https://github.com/wyattoday/wyupdate ?I only ask this second question because I see a PR on it for this issue that isn't accepted yet.
Thank you!
LiptonI'd also be interested in the answer to the questions above.
Right now it looks like none of our users will ever receive an update again. Seems like everybody has to download and install a new version of our product from scratch including a version of wyUpdate that needs to be different from what's provided here. 😐
This has been discussed multiple times on here. wyUpdate already supports TLS 1.2. Use the .NET 4.0 version of wyUpdate and ensure your .NET Framework is up-to-date: https://wyday.com/wybuild/requirements.php#wyupdate
And yes, that's currently the publicly visible repository holding our code. Code is pushed there after private development. Meaning you're not seeing the latest snapshot.
As you say this has been discussed many times. I am now getting the same issue and everything has worked fine for years.
I have my update deployed on a managed server and it is fully up to date with all Windows updates and with the latest support for TLS 1.2 / 1.3 I have ensured the registry default is set for 1.2. The test reports on the server show it is supporting TLS 1.2 fine.
I have built the update with the setting to support the 4.0 .Net framework. None of these fixes the issue “The request was aborted: Could not create SSL/TLS secure channel” when the update tries to get seen / downloaded. My customers are reporting this as well.
The file downloads fine when you access it in a browser.
Is there something I am missing as nothing I have tried over the last few days has fixed it.
Any help here from anyone, greatly appreciated.
