• 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 Let's Encrypt Wildcard by default

Mauzer

New Pleskian
Server operating system version
CloudLinux 8.7
Plesk version and microupdate number
18.0.49
By default it seems that Let's Encrypt will only secure the main naked domain, www and webmail, as per my first screenshot-1

However, our situation is different and we need to Wildcard secure all domains by default (when created) and then assign the certificate to the mail domain, as per screenshot-2

I cannot for the life of me see where to set this in Plesk.
 

Attachments

  • ssl-1.png
    ssl-1.png
    68.5 KB · Views: 8
  • ssl-2.png
    ssl-2.png
    71 KB · Views: 8
I am trying hard to understand the question. On screenshot ssl-2.png you show where to opt for the wildcard certificate solution, but your text says you cannot see where to set this in Plesk. Could you please rephrase the question as it seems to be answered by screenshot ssl-2.png already?
 
Basically I want a new subscription/domain to be created with a wildcard SSL by default, as soon as it is set up in Plesk, and that same wildcard certificate must be assigned to the mail domain, as per ssl-2.png.

At the moment the client has to log in and do this himself, because only domain.com www.domain.com and webmail.domain.com is secured.
 
To me, it's a nice to have but not back breaking since some I sometimes would like to use an email address that's not associated with the subscription for better tracking so doing it at the time of the SSL certification creation is better then having to remember to go in and manually update it after the automatic process of the domain creation is done. Just my honest opinion.

But I agree, please vote for the feature request on user voice.
 
Back
Top