1471 results found

1. Pagination support for Console Log in Docker extension

   Details: https://talk.plesk.com/threads/ui-freezing-in-docker-containers-detail-page.368573/

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docker  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

2. DKIM Weekly Rotation of key, with new 'selector' where previous selector is removed the next week

   As in:
   https://proton.me/blog/dkim-replay-attack-breakdown

   Rotating DKIM is highly important.

   Currently, it' **** easy to rotate the DKIM key on Plesk, not to talk of updating DNS and running Route 53 update.

   This is asked to be implmented, where a second key is added, and new mails use it.

   Old key would be depreciated a week later, as previous emails are still in the progress.

   Rotate your DKIM keys regularly – Rotating our DKIM keys allowed us to quickly stop the attack and buy time for the permanent solution. Although tedious and risky to do manually, Proton’s DKIM key management system(new window) allowed us to easily do this in minutes, and this system is the same system used for all domains hosted at Proton. The system also automatically rotates keys regularly to reduce the risk of key compromise.

   As in:
   https://proton.me/blog/dkim-replay-attack-breakdown

   Rotating DKIM is highly important.

   Currently, it' **** easy to rotate the DKIM key on Plesk, not to talk of updating DNS and running Route 53 update.

   This is asked to be implmented, where a second key is added, and new mails use it.

   Old key would be depreciated a week later, as previous emails are still in the progress.

   Rotate your DKIM keys regularly – Rotating our DKIM keys allowed us to quickly stop the attack and buy time for the permanent solution. Although tedious and risky to do manually, Proton’s DKIM key management system(new window)… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

3. Oversign Emails' DKIM From, To, and CC headers

   As in:
   https://proton.me/blog/dkim-replay-attack-breakdown

   Oversign From, To, and CC headers – Most DKIM implementations always sign the From, To, and CC headers if they are present in an email, preventing them from being modified if the message is resent. However, if these headers are missing, they are often unsigned, opening the door to replay attacks with forged headers that make the fraudulent emails seem legitimate. Oversigning mitigates these attacks by signing these sensitive headers in all cases, even if they are blank. If you use Proton to send your email, this oversigning is done for you automatically by our mail servers.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Security  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

4. Custom Temporary Domain Names

   When you create a new site, you get the amazing option to generate a Temporary domain name.

   However, these are randomly generated, which makes finding your dev site difficult, especially if you have a lot of them.

   I get that you can change the domain after creation, but hopefully it won't be such a large change to the plesk code to allow you to alter the domain name at creation from "silly-lalande.90-65-15-200.plesk.page" to "(custom-website-name).90-65-15-200.plesk.page"

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

5. Option to set RTL instead LTR text while editing Plesk notifications

   Implement an option to set RTL instead LTR text while editing Plesk notifications. Useful for certain languages, like Hebrew.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   This is a valid idea. 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.

   -- PD

6. Installation of TYPO3 and Toolkit similar to WP Toolkit

   Our customers wish to install TYPO3 websites after buying an abonnement through WHMCS or the Plesk panel and have a toolkit where they can manage their TYPO3 installations from a panel like WP Toolkit. I searched through all feature suggestions but I didn't find a suggestion. You should be able:
   - to rollout TYPO3 installations
   - to manage all your TYPO3 installation
   - to update your TYPO3 installation
   - to stage/test their TYPO3 installation
   - to remove your TYPO3 installation
   - to reinstall your TYPO3 installation

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

7. wordpress toolkit table prefix mixed case fix/patch

   I'm not sure if it's still the case but the toolkit used to (possibly still does) create table prefixes with mixed case characters (or this is done via the security checkup for existing tables).

   Unix is case sensitive, windows is not.

   MariaDB

   lowercasetablename=0 default for Unix = stored as provided and case-sensitive. $tableprefix = '7a6pcDc' will be stored as 7a6pcDctablename in the DB
   lowercasetablename=1 default on Windows = uppercase changed to lowercase but still case-insensitive $tableprefix = '7a6pcDc' will be stored as 7a6pcdctablename in the DB.

   This is mostly fine with normal database transactions SELECT/DELETE etc but this will fail for the following scenarios

   Scenario 1: Elementor Plugin checks to see if PREFIXeevents exits and then uses an identical check !== to see if they're identical comparing against the prefix in wp-config and expected table name against what the column name is and then attempts to create the table if it's not there.

   Unix results in 7a6pcDceevents !== 7a6pcDceevents (returns false and doesn't try to create the table)
   Windows results in 7a6pcDceevents !== 7a6pcdceevents (returns true, tries to insert table and errors)

   Scenario 2: Migration from Windows to Unix, previously mixed case table names would have been changed to lowercase when creating tables but still works. However when migrated to Unix this would fail as 7a6pcDc_ doesn't equal 7a6pcdc_

   Suggestion:
   If mixed case table prefixes is still a feature, then Plesk needs to recognise what environment it's being used in, it should restrict itself on Windows to lowercase characters only or know to store the prefix value in wp-config.php (and Plesk tables) as lowercase as this is the default install settings for MariaDB in Plesk.

   If this isn't still a feature (table prefixes are all now lowercase) and/or for fixing historical installations. There also needs to be a way to remedy this problem. The prefix isn't editable via the wordpress toolkit once set and causes problems if you try to edit it from within wp-config.php

   For some reason uservoice is removing underscores from some words, apologies.

   I'm not sure if it's still the case but the toolkit used to (possibly still does) create table prefixes with mixed case characters (or this is done via the security checkup for existing tables).

   Unix is case sensitive, windows is not.

   MariaDB

   lowercasetablename=0 default for Unix = stored as provided and case-sensitive. $tableprefix = '7a6pcDc' will be stored as 7a6pcDctablename in the DB
   lowercasetablename=1 default on Windows = uppercase changed to lowercase but still case-insensitive $tableprefix = '7a6pcDc' will be stored as 7a6pcdctablename in the DB.

   This is… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for this idea. It is a valid claim. 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.

   -- PD

8. Plesk Admin Login - Enable IP Address Locking. In other words, like a firewall, specify the IP address source

   Plesk Admin Login - Enable IP Address Locking. In other words, like a firewall, specify the IP address source.

   This simply eliminates concerns about password hacking as a Dedicated IP (source location) can be specified just like Remote Desktop.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

9. Add an icon on the Websites and Domains dashboard, under Status with the other icons, that shows the status of SSL whether it is active

   Add an icon on the Websites and Domains dashboard, under Status with the other icons, that shows the status of SSL whether it is active or not.

   Hover over shows the Expiry date, but that is not essential. Knowing if SSL is active at a quick glance is.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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.

   -- PD

10. Force port 587 for submission

    I would like to have the option to force users to use port 587 for submission, so they can't use port 25 to submit email, and this port 25 is only used for relay between smtp servers.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Mail  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

11. Joomla Toolkit provide sortable site list

    Allow for the sorting of websites by name, traffic, size, and subscription type.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

12. Option To Auto Add Cloudflare IPs To Fail2Ban Whitelist

    Add the option to auto add Cloudflare IPs to Fail2Ban whitelist. A simple check box in the Fail2Ban management panel that will add a Cron job similar to the one described here: https://talk.plesk.com/threads/cloudflare-whitelist-scripts-for-fail2ban-and-nginx.361572/ .
    This is something that will help a lot of people using Cloudflare and it's relatively easy to implement.
    Thanks.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

13. Add the ability to require 2FA for accounts.

    Many sites and online providers today require the use of 2FA to secure accounts. It would be great if Plesk could require the same thing (at least for administrative accounts). I think this could really help increase the security posture of the software.

    As it stands now, Google Auth is optional, and a user has the ability to enable/disable it at will, which isn't ideal.

    According to this thread, there are currently areas where 2FA wouldn't currently be possible, but all of these issues have already been solved by other companies. I have no doubt that Plesk could do it as well.

    https://talk.plesk.com/threads/is-it-possible-to-force-2fa.369633/

    Many sites and online providers today require the use of 2FA to secure accounts. It would be great if Plesk could require the same thing (at least for administrative accounts). I think this could really help increase the security posture of the software.

    As it stands now, Google Auth is optional, and a user has the ability to enable/disable it at will, which isn't ideal.

    According to this thread, there are currently areas where 2FA wouldn't currently be possible, but all of these issues have already been solved by other companies. I have no doubt that Plesk could do it… more

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Security  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

14. Allow the creation of forbidden domain names via API

    Please implement an option in Plesk, which allows the administrator to create domain names, which are forbidden for creation via Plesk UI.

    For example, *.example.com has been added in Plesk > Tools & Settings > Prohibited Domain Names. This limitation should apply to all users in Plesk UI, but the administrator should still be able to create *.example.com subdomains via API calls.

    This will be useful when looking to automatically provide users with a free subdomain for hosting, but prevent them from creating unlimited number of *.example.com subdomain via Plesk UI.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

15. Trigger to update PECL extensions automatically by Plesk

    In recent Plesk versions it is now possible to manage PECL extensions for PHP directly in Plesk. However we need a method to keep such PECL extensions up-to-date, either with some sort of trigger or event handler.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Web / PHP  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

16. change ALL "http"- to "https"-connections for Plesk-updates and -upgrades

    Change ALL "http"- to "https"-connections for Plesk-updates and -upgrades:

    http://autoinstall.plesk.com
    http://archive.ubuntu.com
    etc…

    This is an unforgiveable severe security bug!

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! We will consider this functionality in upcoming releases.

    -- PD

17. Set LVE to "unlimited" for users created temporarily on Migration to speed up Migration on CloudLinux

    The CloudLinux employs several techniques to limit performance, among others "LVE" limits. These are limits on resource usage such as CPU speed, RAM, I/O speed, number of processes, etc.. It is an established fact that the Plesk Migrator is capable of modifying CloudLinux components to allow the Migrator to do it's job, like disabling CageFS for the source user and target server. So, it stands to reason that the Plesk Migrator could also modify these LVE limits to improve performance of the data-transfers to the target server. The I/O limit of 1 MB/s is an LVE default limit for users that are not assigned to a Service Plan. Our suggestion is that the Plesk Migrator sets the LVE to "unlimited" for all users that are created specifically and temporarily for the migrator to do it's job. This can be done via a CLI command: lvectl set-user <username> --unlimited We suspect that the Plesk Migrator has knowledge of which temporary username(s) are created, so it would be an easy job to set the LVE limits for that newly created temporary user to unlimited.
    This would greatly increase speed of the transfers.
    This would only be needed if the detected OS on the target and/or source is CloudLinux ofcourse.

    The CloudLinux employs several techniques to limit performance, among others "LVE" limits. These are limits on resource usage such as CPU speed, RAM, I/O speed, number of processes, etc.. It is an established fact that the Plesk Migrator is capable of modifying CloudLinux components to allow the Migrator to do it's job, like disabling CageFS for the source user and target server. So, it stands to reason that the Plesk Migrator could also modify these LVE limits to improve performance of the data-transfers to the target server. The I/O limit of 1 MB/s is an LVE default limit for users… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

18. Umami Analytics

    Integration of selfhosted Umami Analytics
    https://umami.is/

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Web Applications  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

19. Backup installer for Shared hosting or on local machine

    Option for create WP Backup that can easy install on other Servers without Plesk or on local Desktop. Creation for zip file and installer.php like Duplicator Pro
    that supports Multisite Backups

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup / Restore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD

20. "keep secure" should be ON by default for any new Service Plan.

    We and many other companies sell "Reseller accounts", each reseller has its own service plans. We can't control how they create their service plans and if they enable "keep secured" in their plan.

    So in that case, there should be a global keep-secured solution that has nothing to do with resellers' plans.

    An admin should have the option to enable "keep secured" globally so that any newly created domain will be secured once it's pointed to the server DNS. Something similar is working flawlessly in CPANEL. CPANEL users basically do not need to actively install an SSL by Let's Encrypt. It is installed automatically.

    By developing this feature, you will make the overall experience better. Hosting companies who are migrating websites constantly don't need to watch when the DNS will be propagated, it will however be done by the already existing cron job keep-secured.php.

    We and many other companies sell "Reseller accounts", each reseller has its own service plans. We can't control how they create their service plans and if they enable "keep secured" in their plan.

    So in that case, there should be a global keep-secured solution that has nothing to do with resellers' plans.

    An admin should have the option to enable "keep secured" globally so that any newly created domain will be secured once it's pointed to the server DNS. Something similar is working flawlessly in CPANEL. CPANEL users basically do not need to actively install an SSL by Let's Encrypt.… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Business Logic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your idea! 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.

    -- PD