• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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