• 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.

Question Wildcard SSL/TLS certificate for subdomain

_Andreas_

New Pleskian
I have a certificate for *.example.com
I want to use this on a Webspace sub.example.com
After installing it it shows in plesk under SSL/TLS Certificates;

Wildcard SSL_TLS certificate -> not secured
*.sub.example.com

To have it working I would expect there *.example.com

Is this setup supported at all ?

Background:
I have already a Webspace example.com
and I cannot make there a subdomain sub.example.com for organizational reasons.
Thats why I set up sub.example.com as (main) Webspace
 
The Page is valid when opening with a browser, no certificate errors.
Looks like just to be an issue with the plesk GUI.
 
....Background:
I have already a Webspace example.com
and I cannot make there a subdomain sub.example.com for organizational reasons.
Thats why I set up sub.example.com as (main) Webspace
You have possibly answered your own question in that section above.
Let's Encrypt Wildcard Certificates work perfectly in Plesk > IF < you have domains / sub-domains (and all of their associated DNS) setup correctly.
We have lots, setup as per the last line above i.e. all sub-domains are exactly that; sub-domains of domains. We have no issues at all and never have had.
You may need to re-think those 'organizational reasons' and /or make any required changes to your current setup.
 
Back
Top