• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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