• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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