• 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 www alias not secured by Letsencrypt wildcard

Dukemaster

Regular Pleskian
Hi,
after upgrading to Obsidian I had the problem that the wildcard certificate doesn't support the www subdomain of an alias. In other words, it's not possible to use a wildcard certificate for the www subdomain of an alias.
I can only secure it by normal certificate (old way).

Is there another possibility to secure it by wildcard?
 
@TimReeves, I think you misunderstood the issue. Imagine: example.com is the main domain and has various subdomains, such as "www", "test", "something".

Then you add an example2.com as an alias to example.com

Automatically, "www", "test" and "something" subdomains will also work for example2.com.

But the issue is that Plesk doesn't request a Let's Encrypt certificate for them, as it should. It only requests certificates for "example.com", "www.example.com", "test.example.com", "something.example.com" and "example2.com".

It's a big issue actually, as even "www.example2.com" doesn't get a certificate.

This is a known bug (EXTLETSENC-722) and will, hopefully, be resolved soon...
 
Back
Top