Also, maybe test with Synapse or with FPC's HTTP client to help narrow down whether it's Indy, the SSL libs, or something else.
checked, in synapse ssl working
Make sure you also have the libssl .so in addition to the libcrypto .so.
ls -l /lib64/libssl*
-rwxr-xr-x 1 root root 385952 mar 10 08:54 /lib64/libssl3.so
lrwxrwxrwx 1 root root 13 dec 3 01:20 /lib64/libssl.so -> libssl.so.1.1
-r-xr-xr-x 1 root root 498544 dec 9 21:23 /lib64/libssl.so.1.0.0
-rwxr-xr-x 1 root root 434176 mar 3 01:21 /lib64/libssl.so.1.1
Update:
Apparently indy does not support libcrypto.so.1.1
If the symbolic link libcryto.so refers to libcrypto.so.1.1, then the Could not load SSL library error occurs.
If you edit IdSSLOpenSSLHeaders.pas like this:
Row: 19483
SSLDLLVers: array [0..8] of string = ('', '.10', '. 1.0.2', '. 1.0.1', '. 1.0.0', '0.9.9', '. 0.9.8 ','. 0.9.7 ',' 0.9.6 ');
Replace with:
SSLDLLVers: array [0..8] of string = ('.0', '.10', '. 1.0.2', '. 1.0.1', '. 1.0.0', '0.9.9', '.0.9.8', '. 0.9.7', '0.9.6');
Loading libcrypto.so.1.0.0 runs currectly and SSL works!
Update:
Because of this editing, loading .so will not be possible and problems can arise on other systems.