• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Let's Encrypt - Can't secure Subdomains

D3nnis3n

Regular Pleskian
Hello,
now that the creation of wildcard certs worked, i wanted to secure my subdomains with it.

The documentation says:
1.Go to Websites & Domains and find the subdomain you want to secure
2. Click Hosting Settings.
3. Select the "SSL/TLS support" checkbox.
4. From the "Certificate" menu, select the wildcard SSL/TLS certificate.
5. Click OK.
This, unfortunatley, fails on step 4 as the wildcard certificate is not listed in the dropdown menu of subdomains but only on the main domain.
 
Yes They have just introduced it . So hopefully all these will get fixed in the coming updates
 
Back
Top