Yes please add let's encrypt domain aliases

it would be very nice. workaround dont works fine

+1

@Sergey L, you forgot to add the other 81 participants, from the two threads on github regarding the same matter which I guess no official noticed ?

Given those ones as well, we would be the tenth placed, given that "volume counts".

Now, regarding ClamAV or Push, don't get me wrong. I would love Push as well, but from a development point of view, SSL is a lot more important than receiving mail notifications 15 minutes faster.

There are also bugs to be fixed as well, so I understand that, like the backup manager issue in which setting a volume size, to incremental backups, makes all backups be full instead incremental.

Best regards and please keep us updated.

@Eduard Duluman,

As stated below, lets encrypt improvement will be our next priority. Just that the team capacity is limited and we cannot do everything simultaneously. :)

We recognize the pain of those who uses domain aliases and want to improve it.

As for "our secret plan" just let me repeat here my response from Facebook - there is no "secret plan". Beyond our assurance there are two things to consider:
- even if all supporters of the feature will upgrade, 118 upgrades isn't really a volume to notice comparing to overall number of Plesk licenses.
- as Lets Encrypt module is open sourced, literally everyone could add domain aliases support and break "our secret plan" of making users pay for extra domains in license. :)

As for comparative importance of ClamAV or Push - it is very subjective. Probably ClamAV or Push supporters won't agree with you. This is why we are relying on volume of counts to judge

My opinion is, as stated on github as well, that Plesk is waiting this one out as much as possible so people can add the domain aliases as normal domains ( so then you can use Let's Encrypt ) and implicitly use one domain from your maximum number of domains, based on your Plesk license type.

If domain aliases would be added, they will loose quite a few plesk licenses upgrades... it's a marketing strategy. The other panels which are free, already have this option because it's useful for their users, and they don't gain anything out of not implementing it.

Plesk simply makes me wonder why they refuse to reply on such important feature... while replying to others not really important like ClamAV, when there are already two AVs, or mail push services... while also important, it's not important as this.

I'm telling my clients it's a Plesk limitation not being able to use certificates for domain aliases, on whitelabeled products.

Peace out.

I'm finding myself in a very weird position in which I have to consider dropping my 3 Plesk subscription licenses, two WEB PRO and one WEB HOST, in favor of going back to cPanel. I thought going away from cPanel to Plesk given it's new Onyx release is worth the hassle but.. I for one, am missing few key features.

Me to

Weird we have no official feedback on this one..

Any progress? What's taking so much time?!

Waiting for this also!

Waiting for this also!

should have

+1

And similar/connected topic: https://github.com/plesk/letsencrypt-plesk/issues/19

Please take into account, that there are far more voters on github!
https://github.com/plesk/letsencrypt-plesk/issues/28

+1

+1! Very improtant!

+1 (DirectAdmin has this already covered...)

Like I stated earlier, even webmin/virtualmin/usermin offer this now. For free. It's getting to be shameful that a paid controlpanel like plesk/odin doesn't even offer us the option to use letsencrypt certs the right way. They're waiting it out, so they can make as much money as possible on silly expensive certification. Probably in bed with some CA. Now they're waiting for open source coders to write this FOR them, if that's not a sign of laziness, then I don't know what is, Odin!

+1 !