Skip to content

Feature Suggestions

← Your Ideas for Plesk

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.

For technical assistance, contact Plesk support
For questions, bug reports, discussions and free assistance, check our Forum and Facebook page
For additional information, see Documentation, Knowledge Base and Blog
Follow us on Twitter for more news on Plesk development

Off-topic posts will be removed from here

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

18 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    96 comments  ·  Extensions  ·  Admin →

  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    24 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    The 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

  3. Two factor authentication (2FA) for Service and Additional Admin Accounts

    Currently Plesk supports Clef and Google Authenticator for Plesk admin accounts.

    However if a customer creates additional user accounts (service accounts with owner rights for example) the 2FA option is not available.

    We would appreciate this feature especially in combination with multi-server management, where one customer may have multiple admins and multiple domain subscriptions.

    -Philipp

    113 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    35 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    We are glad to announce the new Multi-Factor Authentication (MFA) extension (https://www.plesk.com/extensions/mfa/), coming to Plesk Obsidian 18.0.61 and later. The new extension is meant to offer seamless 2FA authentication to all Plesk users, and comes with one of the following benefits:

    • Multi-factor authentication can now be configured in the profile settings for users of all levels (administrators, additional administrators, resellers, customers, and subscription users).

    If you have any feedback on the implementation of this feature, please let us know on the forum: https://talk.plesk.com/.


    — AY

  4. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    31 comments  ·  Extensions  ·  Admin →

  5. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    23 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Great 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

  6. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Extensions  ·  Admin →

  7. ability to disable Wildcard certificate option in Let's Encrypt

    Add ability to disable Wildcard certificate option in Let's Encrypt

    19 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    15 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Available 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

  8. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Hi,
    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

  9. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →

  10. Rename Google Authenticator extension

    It's the TOTP implementation so it does not only work with Google Authenticator.
    Call it like 2-Factor-Auth (or something similar) instead

    13 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Extensions  ·  Admin →

  11. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    7 comments  ·  Extensions  ·  Admin →

  12. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Extensions  ·  Admin →

  13. Plesk Email Security for CloudLinux

    Add support for Plesk Email Security extensions on CloudLinux

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Extensions  ·  Admin →

  14. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    5 comments  ·  Extensions  ·  Admin →

  15. Reset secret for Google Authenticator on re-enabling.

    Currently, if you disable 2FA and enable it again for the same account, the same secret is used (from psa db). That is a security risk because if 2FA was disabled due to the fact that a phone was lost. The next time 2FA is enabled for the same account a new secret should be generated. Otherwise, the lost phone still will be able to generate a valid code.

    Implement this feature to be default behaviour or at least add a button "regenerate secret".

    Related links:
    https://talk.plesk.com/threads/how-to-disable-google-multi-factor-authentication-in-mysql.312675/

    https://support.plesk.com/hc/en-us/articles/213407229-Cannot-disable-Multi-Factor-Authentication-for-a-customer-in-Google-Authenticator-in-Plesk

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →

  16. Mail Log Browser show logs to users

    Possibility of the extension "Mail Log Browser" show the logs to users

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    We are happy to announce that the ability to Track Email Delivery is now available in Log Browser 1.8.0. In the new version, Plesk customers (as well as Plesk administrators) can track email delivery and manage deferred emails right in the domain card (under the "Mail" tab).

    You can find additional information at https://docs.plesk.com/release-notes/obsidian/change-log/#log-browser-1.8.0.

    If you have any feedback on the implementation of this feature, please let us know on the forum: https://talk.plesk.com.


    — AY

  17. Please take back MagicSpam as an extension in Plesk!

    Please take back MagicSpam as an extension in Plesk!

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →

  18. 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 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Extensions  ·  Admin →
  • Don't see your idea?

Feature Suggestions

Categories

Feedback and Knowledge Base

(thinking…)