• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue domain:8443 NET::ERR_CERT_COMMON_NAME_INVALID

Alaa Mansour

Basic Pleskian
Dear all

i have a server ( server.domain.com ) protected by Let's Encrypt and I can access server.domain.com:8443 without any problem.

But i can't access domain.com:8443 or costumer.com:8443

it gives me this error:NET::ERR_CERT_COMMON_NAME_INVALID

the error because the certificate of ( costumer.com:8443 ) does not match the certificate that shown ( server.domain.com )

why would (costumer.com:8443) holds the server.domain.com certificate, even though I can access: costumer.com with its own certificate

any idea?
 
Last edited:
but I can't also secure any WWW for a subdomain on my server
for example : www.server.domain.com
or www.subdomain.costumer.com
it gives me the following error:

Warning: Failed to resolve the challenge for www.server.domain.com.
Details
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/XXXXXXXXXXX
Details:
Type: urn:acme:error:connection
Status: 400
Detail: unknownHost :: No valid IP addresses found for www.server.domain.com

strange that I can't resolve the A record on www.subdomain.domain.com, even though I'm using (*) ( ) (@) (www) (domain.com) every possibility all pointed to the server IP
 
PS: i have added the following lines to Panel.ini
[ext-letsencrypt]
renew-before-expiration = 45
rsa-key-size = 4096
 
Back
Top