When adding a subdomain, it takes (at least at my webhoster) 15 min before the changes take effect. If one checked 'Secure the domain with Let's Encrypt' on the page 'Add a Subdomain', an error is thrown because the newly created subdomain is not available in time.
Therefore, I suggest taking this 'feature' off the 'Add a Subdomain' page.1 vote
The time required for subdomain to become available depends on a many factors. In your particular case it takes a long time, in lot of other cases it works fast. Hoster can configure the server to wait longer, so, the feature can works even in your case.
That’s why we have no plans to remove this.
But anyway, everyone, please continue voting for this feature if you consider it important. If we’ll see a lot of votes for this request, we’ll reconsider it.
By default, the Let's Encrypt extension pre-selects all alias domains of a domain to be included in the Let's Encrypt certificate. This can lead to some unwanted results, for example when one of the alias domains is removed from the DNS at a later stage (because it was only used for testing) which would result in Let's Encrypt being unable to renew the certificate.
It would be nice if there was an option that allows us to configure that alias domains should not be selected by default in the Let's Encrypt extension.1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
Remove default certificate and set Let's Encrypt certificate as default when securing Plesk login page
When securing Plesk with Let's Encrypt, the default certificate should be removed and/or the generated Let's Encrypt certificate should be set as the default one.
Such Let's Encrypt certificate should be automatically applied to mail too, and in such case, if server hostname is changed later, that certificate should be automtically reissued, or at least a warning should be generated.1 vote
Currently, to install a manual certificate:
- Copy private key, paste private key, update Cert and CA
- Go to Web Settings, change certificate to new one
- Select "Add Certificate" option next to the certificate
- Private key automatically reused (perhaps read-only or hidden by default)
- Name, Insert/Upload Certificate and CA
- Show a "Replace certificate" option, that will update the domains that used the original certificate.
- Don't see your idea?