I found a problem.
The problem is this.
http://www.pilotlogic.com/sitejoom/index.php/forum/pl-indy/3329-could-not-load-ssl-library
How to find a solution?
IMHO the problem is SSLv2. Which is exactly the same problem as for mbdev.
Solution : see
https://indy.fulgan.com/indy10.changelog.txt [ rev r5303 ]
Updating OpenSSLVersion() to call SSLeay_version() even if LoadOpenSSLLibrary() failed, as long as SSLeay_version() was able to be loaded, at least.
Updating TIdSSLContext.SetSSLMethod() to raise an EIdOSSLGetMethodError exception if the selected SSL/TLS method is not available at runtime. The SSLv2, SSLv3, SSLv23, and TLSv1x methods are now all marked as non-critical when loading the OpenSSL library, since it is not known at that time which method(s) will actually be used at runtime, and not all platforms support all protocol versions. In fact, it is becoming common that SSLv2 is now disabled and may not even be exported on all platforms, so Indy cannot mark SSLv2 methods as critical anymore. Making SSLv3 and SSLv23 as non-critical for good measure.
Adding new IsOpenSSL_SSLv2_Available(), IsOpenSSL_SSLv3_Available(), IsOpenSSL_TLSv1_1_Available(), IsOpenSSL_TLSv1_2_Available(), and IsOpenSSL_DTLSv1_Available() functions.
So, update to a newer version of Indy, or modify your own version (seems to be a codetyphon one) according to the r5303 patch.
*** Edit *** According to Remy Lebeau, you can also modify IdSSLOpenSSLHeaders.pas concerning the loading of the SSLv2 functions:
@SSLv2_method := LoadFunction(fn_SSLv2_method,False); //Used by Indy
@SSLv2_server_method := LoadFunction(fn_SSLv2_server_method,False); //Used by Indy
@SSLv2_client_method := LoadFunction(fn_SSLv2_client_method,False); //Used by Indy