Resolved How to disable Let's Encrypt wildcard support?

[Bitpalast]

It seems to be a feature request on user voice only
ability to disable Wildcard certificate option in Let's Encrypt

But it would indeed be very important to be able to disable this feature. It is not only causing many additional support requests by customers who see the option, but get an error when clicking on it (as the DNS module is not installed), but it seems to cause issues when updating extensions, too. We are now occassionally seeing update installation error messages on extensions claiming that the Plesk DNS module is not installed and the extension requires it to work properly. The only extension that can be meant is the Let's Encrypt extension.

So all in all, I think it was not such a good idea to not to provide an option to disable wildcard support.

 

[Brujo]

Hi @Peter Debik
afaik in the moment only if you disable it in the panel ini, see:Getting Free Wildcard SSL/TLS Certificates from Let’s Encrypt

but this would mean you fall back to the "old acme v1" method and I did not found something about it how long it will be supported

 

[Ruslan Kosolapov]

Hi.

1. yes, for now the only way to hide the wildcard option is fall back to ACME v1
2. in the next release we plan to hide (automatically) the wildcard option if DNS is not available. It should cover most complains on this topic.
3. after that we plan to introduce a panel.ini setting to hide the wildcard option - a lot of people really don't understand what is this, so, ability to hide this looks quite reasonable.

 

[Bitpalast]

@Ruslan Kosolapov While we are at it, could you please have a quick look at
Issue - Probably auto-installer issue since Let's Encrypt "wildcard" update
I think it is related to the latest Let's Encrypt update, too. It's never been seen before, but this error comes up on all systems since the last Let's Encrypt update.