-3
Certificate installed on this site - https://seeklay.icu
-3
Certificate installed on this site - https://seeklay.icu
1
$ openssl s_client -connect seeklay.icu:443 -servername seeklay.icu | openssl x509 -text
...
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=BE, ST=Some-State, L=Copenhavn, O=HGZ, OU=HGZ ROOT CA, CN=HGZ ROOT CA
...
Subject: C=US, ST=Some-State, O=Internet Widgits Pty Ltd, CN=seeklay.icu
...
X509v3 extensions:
X509v3 Authority Key Identifier:
0.
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Subject Alternative Name:
DNS:seeklay.icu
X509v3 Authority Key Identifier:
0.
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Subject Alternative Name:
DNS:seeklay.icu
This certificate is wrong in multiple areas:
0.
is just wrong. It should be a unique identifier.
CA is not a mistake – SeekLay – 2019-09-14T03:15:44.420
If this isn't a self-signed cert ... Do you have the full certificate chain and references to it in the web server config? Do the browsers have the CA listed as a trusted CA with the correct signing key? – ivanivan – 2019-09-14T03:58:43.027