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
11 results found
-
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)128 votesHello, everyone. This functionality was introduced with SSL It! 1.4.0:
[+] The extension can now secure webmail on domains without web hosting.You can install Let's Encrypt on webmail.example.com with/without hosting and regardless of whether the main domain resolves on the local server or not.
-- SH
-
SSL Cert for a Domain with 301/302 redirect
Currently, we can't create a SSL certificate with SSLIt/Let's Encrypt for a domain, when this same domain redirects to another.
For example, if I redirect domainA.com to domainB.com, and I want to create a certificate for domainA.com, I get the following error :
Invalid response from https:/domainB.com/.well-known/acme-challenge/8dDWrjssqI1cLpY4CqkJaWNnpjoc5Pv9aBa4Sigiqqs : "404 Not Found
The requested URL was not found on this server."The problem is that the check is made on the target domain, and not the domain in Plesk, because even the .well-known/acme-challenge gets forwarded.
For now, we are using this workaround (please see attached file)
But we think that Plesk…
9 votes-- PD
-
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.
5 votesIn a test I could not verify that Nginx is restarted. Instead if reloads the configuration which does not cause a downtime. If you are still experiencing an issue with this, please open a ticket with Plesk support so that the issue can be investigated and fixed on your server.
-- PD
-
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
5 votesWhen the "Keep website secured" option is checked in the SSLIt extension configuration page (where the other configuration parameters of the certificate are configured, too), an SSL certificate will be auto-renewed or auto-created when a previously deactivated domain becomes active again.
-- PD
-
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 votesSince version 1.12.0 of the SSLIt, published January 17th, 2023, the extension provides a bird view of all SSL certificates including their expiration dates.
-- PD
-
add posibility to secure webmail with Let's Encrypt certificate for the subdomain with 'No web hosting' type
The issued certificate should be also available for selecting in Domains > subdomain.name > Mail Settings > SSL/TLS certificate for mail
3 votesVerified that it is possible to create a certificate for the webmail subdomain although the hosting type is set to "no web hosting".
-- PD
-
Ability to export/extract certificate for domain with cli,
certificate cli utility does not have ability to download/export certificate. It requires to export/extract certificate for domain with cli.
1 voteThere is no need for such a feature via "plesk bin" or similar constructs, because this can easily be done with openssl on the command line already. Please check results of your favorite search engine and tutorials like https://linuxhandbook.com/check-certificate-openssl/ for the solution.
-- PD
-
Add Secure Website Button For SSL
Be great if you could secure your website directly from the Advanced screen in the SSL section of a subscription. Currently, you have 'Secure Webmail' and 'Secure Mail' buttons but no website. A third button should be added so we don't have to click out of that screen and have to go to the hosting settings page to change the website SSL.
1 voteI tried to find the place that you mention - "Advanced" section - and the buttons you mention, but failed. I can only see a very simply click-path here: On "Websites & Domains" click on "SSL/TLS Certificates", then click the "Install button". You can check all desired options of the certificate and click "Get it free" to install the certificate. If a certificate already exists, a click on "Websites & Domains" > "SSL/TLS Certificates" leads to a page where you can edit SSL settings or click "Reissue" if you want to apply changes to the certificate.
If you require assistance with these or other SSL/TLS options, please desdribe te issue on the Plesk forum https://talk.plesk.com or please contact Plesk support at https://support.plesk.com.
-- PD
-
Add InCommon support for SSL/TLS certifcates
For those who can't use Let's Encrypt or other paid alternative, automatic https://www.incommon.org/ support would be welcome.
1 voteIt would be interesting to know why someone should be limited to use only certificates from one vendor. Anyway, InCommon certs are managed by Sectigo and are ordinary SSL certs. If you do not want to use Let's Encrypt you can easily install any third-party certificate using the "SSL" link in a Plesk subscription or the server SSL settings in "Tools & Settings". You can generate a CSR and also copy-paste your certificate chain and certificate into the SSL manager. This works with your favorite trust center, too.
-- PD
-
Make the SSL certificate upload much easier.
Make the SSL certificate upload much easier - it should not be difficult but it has been engineered to be problematic. I have not had issues with this task before - only when using Plesk.
No direct support to resolve an issue.1 voteWe made a special Plesk extension SSLit!, which was created specifically in order to simplify the work with certificates for domains as much as possible. Perhaps you didn’t know about it. I strongly advise you to use it and you will see that working with certificates in Plesk has become very simple and convenient.
—
IG -
Adding ssl to *.domain.com, Current ssl for domain.com works only for domain.com not for *.domain.com
Adding ssl to *.domain.com, Current ssl for domain.com works only for domain.com not for *.domain.com
1 voteYou can use wildcard SSL now in scope of LetsEncrypt – https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/websites-and-domains/advanced-website-security/securing-connections-with-ssltls-certificates/getting-free-wildcard-ssltls-certificates-from-let%E2%80%99s-encrypt.79603/
—
IG
- Don't see your idea?