• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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