• 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 Let's Encrypt SSL_ERROR_BAD_CERT_DOMAIN.

Amakesh

New Pleskian
I have 4 domains on 1 VDS server. Earlier Let’s encrypt certificates worked fine for for all of them.
Unfortunately i have now a problem with the certificates - SSL_ERROR_BAD_CERT_DOMAIN.
Qualys SSL Labs shows all of the certificates have Server hostname(rsvix170.gerwanserver.de) as domain name and not their own addresses.

SSL Server Test: solaris-ustronie.eu (Powered by Qualys SSL Labs)
Make your website better

I can reissue the certificates via Plesk, but it makes it automatically and have no possibility to change domain name. Plesk shows no problems with ssl and all below, but if you try to go to eg. solaris-ustronie.eu it will give you SSL_ERROR_BAD_CERT_DOMAIN, because the domain name is still wrong.
I can, of course, use advanced settings and type domain name there and and choose request or self-signed. Tried to do that and choosed request, but generated certificate has only CSR part and private key and unable to use it…

  • Domain solaris-ustronie.eu Secured
  • Domain with the “www” prefix www.solaris-ustronie.eu Secured
  • Webmail access webmail.solaris-ustronie.eu Secured
  • Mail access IMAP, POP, SMTP Secured
  • Wildcard Wildcard SSL/TLS certificate *.solaris-ustronie.eu Secured
  • Server Configuration TLS versions and ciphers by Mozilla enabled

I can, of course, use advanced settings and type domain name there and and choose request or self-signed. Tried to do that and choosed request, but generated certificate has only CSR part and private key and unable to use it…
 
Back
Top