• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Wrong SSL certificate for Subdomains

marruo

New Pleskian
Hello,
after movement to a new server with a different IP, the main domain can be opened in the browser with the correct Let's Encrypt certificate.
But all Subdomains of this Domain are also returning the same Let's Encrypt SSL certificate.
So sub.example.com returns the certificate of example.com
- I have removed and recreated the certificate for the Subdomain with the same result.
- I have also created a new Subdomain with the same result.

In the "Hosting Settings" of the Subdomain, the checkbox for SSL/TLS support is activated and the certificate for sub.example.com is selected in the dropdown.
When connecting to the server via ssh the command
Code:
# dig +short sub.example.com
returns the same IP than
Code:
# dig +short example.com

Has someone an idea what might still be misconfigured that leads to this behaviour?
 
I still don't know, why all the subdomains return the same certificate as the domain. The Subdomain and Domain have the same document root.
The file
Code:
/etc/apache2/plesk.conf.d/vhosts/sub.example.com.conf
contains these lines, to the existing, correct certificate files:
Code:
SSLCertificateFile /opt/psa/var/certificates/cert-kzBnqu
SSLCACertificateFile /opt/psa/var/certificates/cert-lDRBkq

So it seems like this configuration is not used/overwritten and maybe something is wrong with the vhost settings.
Does someone have an suggestion what else to check to identify the source of this issue?
 
That's because you are trying to use two subdomains (www.old) which is not valid per the cert. It's not really a bug since the cert is only valid for one level of subdomain.
 
Last edited:
Thanks for the answer. I found my mistake with a wrong IP adress setting (in the "Tools & Settings" -> "IP Adresses".)
 
Back
Top