• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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