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

Issue Subdomain is not secure with Let's Encrypt

WhiteTiger

Basic Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
18.0.52 Update #3
If when creating the Let's Encrypt certificate I assigned the Wildcard SSL/TLS certificate *.domain.tld, why is the subdomain (created after) still considered unsafe?
Should a new certificate be created for the subdomain?
 
The wildcard certificate is applied to the domain, and if subdomains that are not configured are requested, it works for such subdomains. It does not work for subdomains that have an extra web server configuration by default. However, can you select the wildcard certificate from the SSL/TSL certificate selector drop down in "Hosting Settings" of the Subdomain? If not, the subdomain needs its own certificate. In my opinion that is a much better choice anyway.
 
Back
Top