Are you able to run the program SYSEXV/V5-RDOC0? Give it a URL like https://www.google.com - does that work? Give it the URL you are trying to reach - what is the result?
if you use openssl s_client to connect to the URL, does it use a public certificate authority or a self-signed certificat? From the Natural server’s Linux command line enter:
openssl s_client -connect <url> < /dev/null
for example:
openssl s_client -connect empower.softwareag.com:443 < /dev/null
returns (just showing the first few lines):
CONNECTED(00000003)
depth=2 OU = GlobalSign Root CA - R3, O = GlobalSign, CN = GlobalSign
verify return:1
depth=1 C = BE, O = GlobalSign nv-sa, CN = GlobalSign Extended Validation CA - SHA256 - G3
verify return:1
depth=0 businessCategory = Private Organization, serialNumber = HRB 1562, jurisdictionC = DE, jurisdictionL = Darmstadt, jurisdictionST = Hessen, C = DE, ST = Hessen, L = Darmstadt, street = Uhlandstr. 12, OU = IT, O = Software Aktiengesellschaft, CN = empower.softwareag.com
verify return:1
View the certificates the server sends, particularly “depth=1” such as:
CONNECTED(00000208)
Can't use SSL_get_servername
depth=0 CN = some-server
verify error:num=18:self signed certificate
verify return:1
depth=0 CN = some-server
verify return:1
If these list “self signed certificate” then the server’s certificate issuer is probably not in the Linux default certificate truststore. If so, you need to have the server’s certificate issuer (CA) added to your truststore.
There are many possibilities as to what can cause the HTTPS request to fail, so review the results of the openssl s_client test, and, if you want further assistance, please post the results of the openssl test and the REQUEST DOCUMENT program (or a small program that reproduces the problem) here.
