(09-17-2020, 12:16 PM)ronaldobim Wrote: 1.0.2.21
libeay32.dll
ssleay32.dll
That version of the DLLs should work fine. If you are still getting errors with that version after setting the SSLIOHandler's SSLVersions property, then there is something else going on. You are going to have to dig deeper into the details of the TLS handshake to figure out what is actually failing.
(09-17-2020, 12:16 PM)ronaldobim Wrote: 1.1.1.7
libcrypto-1_1.dll
libssl-1_1.dll
TIdSSLIOHandlerSocketOpenSSL does not support OpenSSL 1.1.x. However, there is currently a pull request in Indy's GitHub repo for a new SSLIOHandler that does. You can download that source code and try it, if you want.
(09-17-2020, 12:16 PM)ronaldobim Wrote: After changing this code below the error changed to:
Error connecting with SSL.
error:14077410:SSL routines:SSL23_GET_SERVER_HELLOslv3 alert handshake failure
That is basically the same error you showed earlier, just being raised from a different area of OpenSSL's code. But without DETAILS, there is really no way to diagnose it for you. "sslv3 alert handshake failure" is a very generic error message, all it means is that the peer sent an alert packet to you, indicating the handshake failed on the peer's end and the peer is going to be closing the connection after the alert. There are MANY things which can cause that to happen.
(09-17-2020, 12:16 PM)ronaldobim Wrote: I made several attempts with the FHandler.SSLOptions.SSLVersions property and all failed.
Then the problem is not related just to the SSLVersions alone. Something else must be going on.