• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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