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.

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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  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.

    307 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    96 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  2. ability to disable Wildcard certificate option in Let's Encrypt

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

    18 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →

    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

  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →

    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

  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  6. Please take back MagicSpam as an extension in Plesk!

    Please take back MagicSpam as an extension in Plesk!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base