Are you facing No SSL/library support: Web Agent installation error?

This guide is for you.

Sometimes our customers report that they receive "no ssl/library support" error while trying to install a Web agent.
Generally, this error happens when the SSL libraries are not installed.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve Web Agent related errors.
In this context, we shall look into how to fix this Web Agent installation error.

Nature of 'No SSL/library support' error

Before going into the steps for fixing this error we will see the cause for No SSL/library support: Web Agent installation error
An error similar to one of the following is seen while installing the Web agent depending on the operating system:

On Unix, Linux, and Solaris systems:

init_ssl(): libssl.so is not available

init_ssl(): libcrypto.so is not available

On Microsoft Windows systems:

init_ssl(): ssleay64.dll is not available (error: 126)

init_ssl(): libeay64.dll is not available (error: 126)

init_ssl(): ssleay32.dll is not available (error: 126)

init_ssl(): libeay32.dll is not available (error: 126)

The corresponding install log shows the following error:

2021-04-08 11:27:09 am_agent_login(): error -26 (no ssl/library support) connecting to https://host1.example.com:8443/openam (https://host1.example.com:8443/openam)

This error occurs when the Web agent cannot load the SSL libraries.
Following are some of the reasons for this:
1. When we try to install a 32-bit version of the agent on a 64-bit system. The 32-bit version of the agent admin tool cannot open the 64 bit SSL libraries.
2. When the SSL libraries are not installed.
If the operating system does not include native OpenSSL packages, we must install OpenSSL.

How to fix 'No SSL/library support' error ?

To begin, we need to ensure installing the appropriate version of the agent. If we have a 64-bit operating system, we must install the 64-bit agent.
Also, we need to ensure either the operating system provides native OpenSSL packages or OpenSSL is installed.
If we are using OpenSSL, we can check that the OpenSSL libraries are in the correct location as follows and add them if they are missing:

On Linux systems:
1. Check that the LD_LIBRARY_PATH environment variable is set:

$ echo $LD_LIBRARY_PATH

2. Check that the OpenSSL libraries (libcrypto.so and libssl.so) are available in the path specified in this environment variable (LD_LIBRARY_PATH).

On Unix and Solaris systems:
1. Check that either the LD_LIBRARY_PATH or LD_LIBRARY_PATH_64 environment variable is set:

$ echo $LD_LIBRARY_PATH

$ echo $LD_LIBRARY_PATH_64

2. Check that the OpenSSL libraries (libcrypto.so and libssl.so) are available in the path specified in the relevant environment variable.
On Microsoft Windows systems:
We need to check that the OpenSSL libraries are in the correct location as follows:
32 bit systems – libeay32.dll and ssleay32.dll files are in the \windows\syswow64 directory.
64 bit systems – libeay64.dll and ssleay64.dll files are in the \windows\system32 directory.

[Need urgent assistance in resolving Linux related errors? We can help you. ]