mezam

??

thanks! I’ll try that right away

many thanks Steve, I have only one web server and with no GUI.

I solved it. The problem relied on SELinux. By default on RHEL is set to “enforcing”. I lowered it to “permissive” and it worked.

and if I try: curl -v https://api.www.ads-software.com
I get:

* Rebuilt URL to: https://api.www.ads-software.com/
* Trying 198.143.164.251…
* TCP_NODELAY set
* Connected to api.www.ads-software.com (198.143.164.251) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, [no content] (0):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; CN=*.www.ads-software.com
* start date: Nov 6 17:42:01 2017 GMT
* expire date: Dec 15 20:11:21 2020 GMT
* subjectAltName: host “api.www.ads-software.com” matched cert’s “*.www.ads-software.com”
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=https://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority – G2
* SSL certificate verify ok.

also.. my openssl is openssl-1:1.1.1-8.el8.x86_64

as specified in initial post, the WP instance is installed on a RHEL 8 server and it’s hosted on AWS