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
14 results found
-
Let's encrypt: add domain aliases
The let's encrypt extension is great, except... it doesn't work for me: It doesn't add domain aliases. I have domains like "typing-error.de", "typing-eror.de", "typing-errror.de", "typing-error.com" etc. (you get the idea). As-is, only the primary domain is added to the certificate.
305 votesLet’s Encrypt 2.0.0 extension with this feature is now available!
https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt
We would love to hear your feedback on our forum at http://talk.plesk.com. We’d like to thank everyone who commented on this request and provided invaluable feedback. Thanks!
-
Support full DNS for CloudFlare ServerShield
Currently CloudFlare ServerShield is implemented using partial (CNAME) setup. What is the point in a partial setup when you can benefit from full DNS? You get anycast DNS with CloudFlare on full DNS.
151 votesThe DNS Integration for Cloudflare extension is production-ready since Plesk 18.0.56, published October 10th, 2023. Empower your experience with simplified DNS synchronization, enhanced website security, effortless subdomain creation, and smoother workflows. Use Cloudflare CDN, which distributes content around the world to speed up websites.
- Connect your existing Cloudflare account to Plesk.
- Import DNS records from Cloudflare to Plesk.
- Export DNS records from Plesk to Cloudflare (both manually and automatically).
- Enable/disable Proxy Mode.
This update completes the work on the new Plesk DNS Integration for Cloudflare extension. Please comment if you have additional thoughts on it.
-- PD
-
Generate a deploy key per repo in the Git extension
Currently, the Git extension only generates one deploy key per Plesk user (according to @PleskHelps on Twitter). Unfortunately, GitHub doesn't allow a deploy key to be used more than one time across ALL repos, meaning every single GitHub repo requires a unique deploy key. As a result, I can clone only one of the 40 some repos I would like to on my Plesk installation.
I would like to suggest the option to have a unique deploy key generated for every single repo you want to clone. That would make the Git extension infinitely more useful for me and many…
95 votesThe ability to deploy an SSH key per repository has been implemented in the Git extension 2.3 version.
--AA
-
Multiple users for the Git extension
It would be great if it would be possible to create multiple users which can use the Git repository. Today only one user can access the Git repository. It is the admin user which was created during the creation of the subdomain. New created Web Users for the subdomain can not access the Git repository. It is a feature which I am missing because I wanted to host a private Git repository for our small private team.
https://talk.plesk.com/threads/can-not-create-new-users-for-local-git-repository.342409/
85 votesGreat news! In the Git Extension 2.4.0, published January 26th, 2023, this feature became available:
Previously, only the system user had access to all repositories in a subscription, but now Plesk added the ability to select users who can access a local repository via HTTP/HTTPS.
You can now select additional users when creating a local repository or changing the settings of an existing one. These users can pull and push to a local repository via HTTP/HTTPS using their credentials.
-- PD
-
Ability to issue wildcard certificates via Let's Encrypt CLI
We now have the ability to issue wildcard certificates via GUI, but it would be handy to issue the wildcard certificates via CLI as well
22 votesAvailable since SSL It! 1.4.0 (4 June 2020): https://ext.plesk.com/packages/3c4117f6-c05c-4d3b-9173-60f10096a9c4-sslit#!
-
ability to disable Wildcard certificate option in Let's Encrypt
Add ability to disable Wildcard certificate option in Let's Encrypt
19 votesAvailable since Let’s Encrypt Extension 2.8.3.
https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt
“2.8.3 (24 October 2019)
[+] Introduced the allow-wildcard-certificates option (true by default) under the ext-letsencrypt section in the panel.ini file. If set to false, the option hides the feature of issuing wildcard SSL/TLS certificates in the interfaces of the Let’s Encrypt and SSL It! extensions.Note: For the same purpose, users could earlier use the acme-protocol-version setting with the acme-v01 value. If you have this configuration, we recommend that you start using allow-wildcard-certificates set to false because the ACMEv1 protocol will soon reach end of life."
— rk
-
Add support for ASP.NET Core 2 for Plesk Onyx
Let's support this please. Add support for ASP.NET Core 2 for Plesk Onyx
17 votesHi,
I’m glad to inform you that this functionality was added since Plesk Onyx 17.8 release :) Plesk detects if ASP.NET Core 2 is installed or you can install it as a component via Plesk Installer (Tools&Settings → Updates & Upgrades → Add/Remove Components). Then deploy your ASP.NET Core application to the website document root.
Plesk Onyx Release Notice: https://docs.plesk.com/release-notes/onyx/change-log/-DL
-
SSL it! support latest server-side-tl version 5
I would be nice that the latetst version of mozilla will be supported in the SSL it! extension. It would be even better that we can select for previous configuration (version 4) or recommended configuration (version 5)
13 votesThis functionality is available since the SSL It! 1.6.0 (9 September 2020) extension release, https://docs.plesk.com/release-notes/obsidian/change-log/#ssl-it-1.6.0.
We would appreciate hearing your feedback on implementation of this functionality. Thanks in advance!
—
AY
-
show let's encrypt certificate expiration date
As Let's Encrypt keeps on telling me to renew my certificates and plesk tells me that it automatically rene s 30 days before expiration it would be handy to actually SEE the expiration date on the let's encrypt or on the certificate pages.
11 votesThe feature is available in Advisor extension (Plesk Onyx 17.8) as “Security > Secure Websites With SSL/TLS Certificates” recommendation.
-
Update Node.js Extension to support current versions
The plesk extension is currently delivered with a bit older versions of Node.js (3 months):
- 6.10.2 LTS (plesk 6.9.1)
- 7.9.0 (plesk: 7.4.0)9 votesStarting with Node.JS extension verstion 2.0 the latest LTS versions are downloaded and installed automatically.
If you’d like to help us prioritize further improvements, please share your expectations in this short survey:
https://pt-research.typeform.com/to/LAObHNoi#source=uservoice
Thank you!
AS
-
Plesk Email Security for CloudLinux
Add support for Plesk Email Security extensions on CloudLinux
8 votesAdded since Plesk Email Security 1.2.1 (06 October 2021): https://docs.plesk.com/release-notes/obsidian/change-log/#email-security-1.2.1
--
IG
-
Please Add support for ASP.NET Core 2.1 for Plesk Onyx, thanks
Let's support this please. aspnetcore 2.1 has got the official version, Add support for ASP.NET Core 2.1 for Plesk Onyx
7 votesAdded support for ASP.NET Core 2.2.2 (Plesk for Windows) – https://docs.plesk.com/release-notes/onyx/change-log/#contents-179-preview12
—
IG -
Please take back MagicSpam as an extension in Plesk!
Please take back MagicSpam as an extension in Plesk!
1 voteUnfortunately, not everything depends on us here. There are questions to MagicSpam side, vendor of this extension. The current situation with this you can monitor in this thread https://talk.plesk.com/threads/magicspam-extension-missing-in-extension-catalog-but-installed.348668/
Thanks.
—
IG -
Git extension: allow configuring a default deploy-to directory
Right now, you cannot set the git deploy-to directory until after the repository is setup and deployed the first time. After you "fix" it, it deploys again on the new path, but does not clean up the wrong deployment it did during setup.
I use a "/data/web/htdocs" path for all my customers, and it is painful to reconfigure git deployment for each of them. A default setting would be very nice.
1 voteThank you for your input!
Could you please why you cannot change deploy-to directory via click “to /httpdocs/ directory”
(see right side on screenshot https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/git-support/using-remote-git-hosting.75848/#o76294)?— AY
Upd: Thank you for confirmation. We are closing the request as completed.
- Don't see your idea?