Certificates – The self-signed signatures I've created for localhost are unreliable, even though I've already imported them into Chrome.

Certificate - Other name of the missing subject
The certificate of this site does not contain any object. Other name
extension containing a domain name or IP address.

This average:

  • the CN does not match Server name
  • And the X509v3 Subject Other name not too much field.
Certificate - missing
A valid trust certificate is missing from this site (net :: ERR_CERT_AUTHORITY_INVALID).

This average:

The server could not be trusted because no valid certificate was provided …
Ok, that would be solved when the first mistake would be resolved!

Think of the means (IP address or DNS name) to connect your server:

https://228.929.123.46/

or

https://mydomain.example.com/
https://127.0.0.1/
https: // $ NOMHOTE /

You can create a certificate with

  • CN = 228.929.123.46 and add DNS.1 = mydomain.example.com DNS.2 = $ NAME DNS.3 = 127.0.0.1 DNS.4 = other.domain.org DNS.
  • CN = 127.0.0.1 and add DNS.1 = mydomain.example.com DNS.2 = $ NAME DNS.3 = 228.929.123.46 DNS.4 = other.domain.org DNS.

But if you're on the Internet, you'd better delete the invalid host names, localnet (192.168.x.x) and localip (127.x.x.x)!

  • CN = 228.929.123.46 and add DNS.1 = mydomain.example.com DNS.2 = Other DNS.domain.org.

And use only the DNS address or the public IP address to reach your server!

Take a look there,

So to see how to do that …