• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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