Issue www alias not secured by Letsencrypt wildcard

[Dukemaster]

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]

Well, "www." to a subdomain would be something like "www.mail.example.com". Normally there will be no DNS entry for that, so verification would fail. Maybe it's a feature, not a bug?

 

[Ales]

@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...

 

[Dukemaster]

Well, "www." to a subdomain

Yes, like @Ales wrote, it's about www.example-alias.eu which is an alias for the main domain www.example.com. With wildcard cert I was only able to reach the domain by example-alias.eu without www.
I missed explaining it in more details.