Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
-
Add Mailman support to Let's Encrypt
Please add Mailman support to Let's Encrypt.
Ideally, one could issue either a certificate directly for lists.domain.com or a wildcard certificate for *.domain.com.
Furthermore, a secure connection should be enforceable.
Thanks!
247 votesThank 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.— rk
-
Let's Encrypt: separate cert for webmail (without main domain in SAN)
We have a setup where webmail.example.com and example.com point to another server than our Plesk instance. Because of this we can't enable Let's Encrypt on Webmail since the CSR contains webmail.example.com and example.com.
So I hope you consider adding an option to only create webmail.example.com (without SAN example.com)112 votesThank 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.— rk
-
Allow both HTTP and HTTPS version of websites to be forwarded. It's 2018, this is vital.
This is all about security, it's simply not a fully developed product without this facility and I am hugely shocked and surprised it doesn't already exist.
27 votesThank you for the update! 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.
—
IG -
Automatically apply wildcard Let's Encrypt SSL
It will be good if Plesk can implement automatically applied wildcard let's encrypt option by default.
12 votes -
Uploading purchased SSL/TLS certificate for domains aliases
Hello,
Please add functionality for uploading purchased certificates for securing domain aliases.
At the moment domain, aliases always use the certificate for the main domain. This is not suitable if different certificates are used for a domain and an alias.
Let's Encrypt certificates can be issued for aliases, but certificates uploading should also be possible.
9 votesThank 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.
—
IG -
Option to disable SNI for a domain in SSL Settings
If a domain has SNI disabled from IIS > Site > example.com > Bindings, Plesk reverts it back to Enabled when it pushes changes to IIS.
It would be nice to have an option in the domain's SSL settings to turn ON/OFF SNI and lock it.
9 votesThank 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.
—
IG -
Allow certificate upload as .pfx container
If you have a .pfx file containing Certificate, Private Key and CA certificate, allow to upload that container with one step.
This way, a customer doesnt have to use tools like openssl to extract and convert the certificate themselves.
.pfx is the preferred format on windows plattforms ,e.g. when you export a certificate from another IIS-based server.
9 votesThank 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.
—
IG -
SSL Certificate changes should be reflected in Action Log
SSL Certificate changes are currently not logged in Action Log in any way. Such changes should be logged as they are part of hosting settings.
Yet, they should reflect the certificate details (e.g. "Certificate A was changed to certificate B").8 votesThank 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.
—
IG -
Create CSR with multiple domains
Currently, Plesk only provides the option to include a single domain on a Certificate Signing Request (CSR): https://support.plesk.com/hc/en-us/articles/213939845
According to our business needs, we need to issue a CSR with alternative subject names, we need to include multiple domains on this CSR so we can issue a SAN certificate, but Plesk doesn't have such functionality.
7 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Add the option to remove certain domain names or its parts from Let's Encrypt certificates auto-renewal notifications
Add the option to remove certain domain names from Let's Encrypt certificates auto-renewal failure (customer's digest) and Let's Encrypt certificates auto-renewal success (customer's digest).
For example, I have domain example.com without "www" part (by design) that is secured with Let's Encrypt certificate for example.com (without "www" part). Plesk sends the notification that the www.example.com could not be secured. With the suggested option it will be possible to switch off such notification for "www" part only so that the regular notification for example.com will be active.
7 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
A button to manually reissue SSLs for all domains
Can we get a button to manually reissue SSLs for all domains and subdomains?
I had a few issues in the past year because SSLs didn't automatically renew which made me lose hours with support tickets.
I would prefer to hit the button "Reissue SSL for domains" once every 60 days over relying that everything will just work automatically.
6 votesThank 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.
—
IG -
Use Lets Encrypt to secure preview urls
Hi,
I think the preview urls is a really useful feature, but they have a limitation in which they cannot be secured.
Being able to secure these urls with a wildcard certificate from Lets Encrypt would be hugely beneficial when developing.
An example would be when developing with certain APIs such as HTML5 Geolocation API.
Thanks
6 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Automatically select the certificate in Domains > example.com > Mail Settings > SSL/TLS certificate for mail for newly created domains
When the new domain is created and when the option 'Keep websites secured with free SSL Certificate' is enabled on a service plan level as per: https://support.plesk.com/hc/en-us/articles/115001575134, the certificate is not automatically selected in Domains > example.com > SSL/TLS Certificates for mail, only for 'webmail'.
4 votesThank 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.
—
IG -
Implement a general-purpose ACME client for certificate authorities other than Let's Encrypt
Currently, it is only possible to automatically renew certificates issued by Let's Encrypt. Certificates from other CA's have to be updated manually even if they support ACME protocol, so it would be useful to have a module that could renew all certificates.
4 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
List SSL expiry in domains list
List of SSL Expiry date in domains list, and make it sortable so we can target domains with close expiry.
4 votesThank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
—
IG -
Reload Nginx serivice instead of restaring it when reissuing Let's Encrypt certificate
When reissuing Let's Encrypt certificate for wildcard subdomain(*.example.com) Nginx is restarted, which causes downtime depending on the number of websites. For example, if the server hosts around 4000 domains this can cause 15 seconds downtime for each restart.
The suggestion is to reload the Nginx service and not to restart it.
4 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Add additional CA certificates to an existing certificate
It would be very helpful to be able to add additional CA certificates to existing certificates.
For example, in our case, on a domain with Let's Encrypt, it's required to add origin-pull-ca.pem from Cloudflare (https://support.cloudflare.com/hc/en-us/articles/204899617/) but trying to set sslclientcertificate (Nginx) or SSLCACertificateFile (Apache) as additional directives will trigger an error of duplicate syntax.
Therefore, it should be possible to go to Domains > example.com > SSL/TLS Certificates > Click on the certificate > Add more CA-certs
4 votesThank 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.
—
IG -
Auto-renew Let's Encrypt certificate when domain is reactivated
When a disabled domain with a Let's Encrypt certificate is re-activated in one of those situations, Plesk should be able to:
Situation A: Domain is reactivated before reaching certificate's expiration date => Do nothing, and renew the certificate aproaching the set date in the cert itself
Situation B: Domain is reactivated after reaching certificate's expiration date => Plesk should re-order or renew the expired certificate
4 votesThank 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.—
IG -
Take *.domain.com as the CN of Wildcard certificates in the LE extension
At the moment the CN of the wildcard certificate is still domain.com and not *.domain.com. The wildcard is just in the alternative domain names.
Please use the wildcard as the CN4 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain.
Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain. At this way, Plesk can provide only mail services.
3 votesThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
--
IG
- Don't see your idea?