TLS initialization failed only on a particular machine
-
wrote on 22 Jan 2021, 19:43 last edited by
Hi SGaist! Thanks for your answer. I will check. What should I be looking for?
-
I'd start with checking If there's a certificate that is outdated or missing.
-
wrote on 26 Jan 2021, 07:39 last edited by
Having the same issue. Certificates seems to be valid (clean Win 10 Pro). Any other ideas ?
-
Having the same issue. Certificates seems to be valid (clean Win 10 Pro). Any other ideas ?
wrote on 26 Jan 2021, 14:24 last edited by@Harry-Schneider said in TLS initialization failed only on a particular machine:
Any other ideas ?
You may want to use Wireshark to check the TLS handshake.
-
@Harry-Schneider said in TLS initialization failed only on a particular machine:
Any other ideas ?
You may want to use Wireshark to check the TLS handshake.
wrote on 25 Feb 2021, 15:28 last edited by@Pablo-J-Rogina said in TLS initialization failed only on a particular machine:
@Harry-Schneider said in TLS initialization failed only on a particular machine:
Any other ideas ?
You may want to use Wireshark to check the TLS handshake.
Hi Pablo, thanks for the suggestion. I'm using WireShark to compare the packages between a request that is working and the one is failing, but I don't see any differences at first sight. Do you know if there's anything in particular that I could look for?
Here's the successful request:
And the one is failing:
-
wrote on 26 Feb 2021, 13:35 last edited by
@SGaist @Pablo-J-Rogina Do you know if there's a way to log more information about the error? Because I don't see anything wrong when I analyze the packages with WireShark. Right now I'm using poReply->errorString().
Does it make sense to try updating Qt 6.0? Do you know if the binaries for libcrypto and/or libssl have been updated since Qt 5.15.0? Any other ideas?
Thanks!
-
You test different versions of OpenSSL yourself. They are not linked just dynamically loaded and even if linked, you can switch them.
-
wrote on 11 Mar 2021, 14:45 last edited by
It worked by updating the OpenSSL binaries to OpenSSL 1.1.1j. So it's probably a bug that was solved in that version. Many thanks for the help! Hope this helps someone.
-
It worked by updating the OpenSSL binaries to OpenSSL 1.1.1j. So it's probably a bug that was solved in that version. Many thanks for the help! Hope this helps someone.
wrote on 11 Mar 2021, 16:47 last edited by@fsinisi I had similar problem in the past and I found out that binaries for OpenSSL distributed with Qt are compiled used MSVC, they require additional libraries from MS. Some of the computers that were running my software had them, some of them not.
Problem was solved by using OpenSSL build with MinGW - no dependencies there. -
wrote on 12 Mar 2021, 14:34 last edited by
@artwaw Thanks for the tip!
In this particular case, I think the problem was related to the version because it started to work after updating to OpenSSL 1.1.1j instead of the version that comes with Qt 5.15.0 (which I think is OpenSSL 1.1.1g but I'm not sure now).
I compiled the libraries myself following the official guide which uses MSVC: https://github.com/openssl/openssl/blob/master/NOTES-WINDOWS.md
Anyway, your suggestion makes sense and it is definitely something to try as well if anyone has problems.