This is likely a server configuration error. But you can use WireShark to investigate exactly why the download is failing. Google for tutorials on how to use WireShark.
Error trying to save file: Error downloading "https://DOMAIN/UpdateWin/wyserver.wys":
WelleWe have been using your product for 2 years with no issues. However, recently, updates fail with the error message:
Error trying to save file: Error downloading "http://www.DOMAIN/UpdateWin/wyserver.wys": The underlying connection was closed: An unexpected error occurred on a send.
We have read the thread: https://wyday.com/forum/t/3799/wyupdate-error-downloading/ which pointed out to certificates. However, our server has an active certificate (Let's Encrypt Authority), the one we have been using since the beginning, and all checks report that the certificate is okay.
In which direction should we move to find to make updaes working again?
WelleThank you for the answer. I will habe a look at Wire shark. I do not know how wyUpdate fetches the file, however, if I simply copy and paste the url in a browser, I can download it without problems.
WelleAfter some experimenting, it seems that the problem resides in the area of secure connection. On the same server, working on a domain without https is fine. However, in a domain with https it fails with the above mentioned error. Unfortunately, not having more infos from the error it is not that easy to debug the cause of the problem. Again, certificate seems okay.
Use the . NET 4.0 version of wyUpdate, and use WireShark to see where the connection is failing.
WelleUsing the . NET 4.0 version of wyUpdate, I get the following error:
The request was aborted: Could not create SSL/TLS secure channel
With Wireshark I cannot find any useful information (I must out myself as not expert with the software and related protocols). Server supplier contacted to know if they have changed something (probably TLS versions?)
The easiest solution for now would be to migrate the update server to a non https domain. But how to redirect all client.wyc already out there to the new server? A .htaccess redirect was not lucky. Any suggestion is appreciated, since this is not development but already deployment...
MarkLFTI have the same issue. All servers seem to be disabling SSL/TLS1.0 and TLS1.1, is there a way to may wyBuild use TLS1.2?
Or is there some other workaround?
Yes: https://stackoverflow.com/a/44153734
Use the . NET 4.0 version of wyUpdate.
In the next update well force using the newer TLS protocol by default.
Wyatt wrote:> Yes: https://stackoverflow.com/a/44153734> > Use the . NET 4.0 version of wyUpdate.> > In the next update well force using the newer TLS protocol by default.
Just run into the same error 🙂 And unfortunately we can't ask users to make registry changes... So - the question - what's the ETA on the next update?
Ta, Michael.
Felix123The way i went is to build wyUpdate yourself targeting a higher version of .NET.But take care! wyupdate tries to update itself. --> Create your own repository for wyUpdate updates. This makes the whole system work again in a modern environment.
Need the update ASAP as well. Same error with all my updates. Using version 2.6.18.4. ETA?
"Felix123" are talking about building and including the wyUpdate.exe in the update of your product after targeting .Net4? Tried this and now the error is:"The request was aborted: Could not create SSL/TLS secure channel."
---- Update - Ok, built with all versions of the .Net4 framework and found that 4.6 is the earliest to fix this. However, looks like I will have to push the WyUpdate.exe manually to all of my customers.
Seems that the current version of WyBuild injects the older version of WyUpdate. As this is killing my automation and I need the new version of WyBuild to ensure my products are updating, when will the update be available?