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
426 results found
-
Nginx Cache purge
Please, consider to implement some sort of cache purge functionality available from Plesk web interface, because if cache TTL gets extended to match Site needs, it gets complicated, i.e. need to go over Linux Terminal to purge it. A Wordpress integration would be just super fantastic, but I understand, it is not realistic to wish it.
Thank you!123 votesStarting from Plesk Obsidian 18.0.45 https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18045,
added the ability to manually clear nginx cache for websites with nginx caching enabled, both via the GUI and using the plesk bin domain_pref --reset-nginx-cache <domainName> command.
--AA
-
Support for Windows Server 2019
Please add support of Windows Server 2019 in Plesk Onyx.
4 voteshttps://docs.plesk.com/release-notes/onyx/change-log/#contents-179-preview11
Added support for Windows Server 2019.
—
IG -
Enable/disable debug in Plesk via CLI
The suggestion is to implement CLI utilities to enable/disable Plesk debug:
plesk debug -enable
enabled = on
filter.priority = 7
show.utilexec = on
show.utilexec_io = onplesk debug -enable --sql
The same as previous + show.sql_query = onplesk debug -disable
Now it is necessary to remember panel.ini path (/usr/local/psa/admin/conf/), copy panel.ini.sample, then edit it manually every time. And the same procedure to disable it.
33 votesIt's enough to call the following command:
plesk conf panel.ini
--AA
-
Modify the email sent when a new WordPress site is created
We need to modify the email that is sent to customers, when a new WordPress site is created. I am attaching an example of the email:
Your new WordPress site has been successfully set up at:
https://<site>/wordpress
You can log in to the administrator account with the following information:
Username: created_user
Password: The password you chose during installation.
Log in here: https://<site>/wordpress/wp-login.phpWe hope you enjoy your new site. Thanks!
7 votesWPT 6.0 adds the ability to turn off sending of initial email by WordPress. This can be done in Global Settings. Let us know if you have any feedback.
--AK
-
Add support for MicroSoft Web Deploy 4.0
Web Deployv.4.0 was installed on the server before Plesk.
Now WebDeploy is displayed as installed in Plesk installer.
However, it is not detected by Plesk in Tools & Settings > Server Components(Refresh does not help either).Please add support for WebDeploy 4.0
2 votesWebdeploy 4.0 is shipped with Plesk since Plesk Onyx 17.9, December 18th, 2018.
-- PD
-
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 -
Use ntpd or chronyd to synchronize time instead of ntpdate
Use ntpd or chronyd to synchronize time instead of ntpdate that is deprecated
1 voteThere is NTP Timesync Plesk extension: https://ext.plesk.com/packages/8dece852-7f0f-481c-889f-c74d304d133a-ntp-timesync? Currently, following service backends are supported: chrony ntpd systemd-timesyncd
--
IG
-
Customize Quick installation of Wordpress
It would be great to add ability to customize Quick installation settings of Wordpress. For example,currently it is not possible to change installation path in case of Quick installation option is selected. However it maybe required to modify the path without customizing other options (such as Administrative access credentials, main configuration etc), Having ability to modify default quick installation settings would be a nice tool, which make it easier to use WordPress for end-users.
3 votesWe have redesigned the installation experience, and it seems that installation of WordPress is now working the way you want. Check the feature out and let us know if you have any additional comments!
—AK
-
Enable Mail DKIM signing by default
I suggest to add an option to Plesk Service Plans to enable DKIM signing when creating a new hosting package.
Right now we have to manually enable DKIM signing for every new hosting account after creation.
This should be inside a Service Plan under tab: Mail
14 votesSince Plesk Obsidian 18.0.50 DKIM is turned on for all domains that are newly added and have their DNS managed by the same server.
-- PD
-
indicate password strengh or acceptance during "reset password" process
There are many customers complaining, they have to try several passwords during the password-reset process, before one is accepted. There is no visual indicator if the typed password fits the safety regulations.
"Inside" plesk, the password strengh is indicated when they change theirs plesk- , FTP- or e-mail password. Why not during the reset-process?
The highlight would be an indicator, that permanently shows if the typed password is strong enough or has to be stronger (with a tooltip/hint, what specifications has to be met or which kind of character is missing).
5 votesGood news everyone!
This functionality was added in Plesk Obsidian RTM release. We suggest you upgrade to the latest version and check it out.
—
AA -
Refresh the page in a browser right after detaching a WP instance in WP Toolkit
Right after detaching an instance in Home > Wordpress it remains on the page because the page is not refreshed.
I suggest to invoke page refresh after detaching as it can confuse the customers.1 voteThis issue was fixed in one of the previous WPT releases.
—AK
-
restrict installation of specific paid plugins/themes for WordPress
There should be the possibility to limit access to WordPress plugins/themes per a service plan.
1 voteReleased as “Blocklist” feature in WordPress Toolkit 5.6.0 https://docs.plesk.com/release-notes/obsidian/change-log/#wordpress-toolkit-5.6.0
—
IG -
better backup priority settings to include nice and ionice
Currently it seems the backup priority only takes CPU into account and not I/O
I would prefer the backup low priority settings to be changed into specific values. For example
CPU PRIORITY -> Select Box with options 1-19
IO Class -> Select Box with options 1-3
IO Priority-> Select Box with options 1-71 means realtime and the higher the number the less important is the task.
Then this can be converted into custom commands depending on the user needs like:
nice -n{CPU PRIORITY} ionice -c{I/O CLASS} -n{I/O Priority} <backup task command>
For example one could set like this
nice…
15 votesAlready implemented since Plesk Obsidian version.
—
IG -
Implement renewal of Let's Encrypt wildcard certificates
Please implement renewal of Let's Encrypt wildcard certificates through Plesk or command line.
69 votesAvailable starting Let’s Encrypt 2.7.0: https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt
-
Restart services on failure using systemd
We've noticed that Plesk services like plesk-php72-fpm are sometimes killed by the out of memory killer or otherwise crash and require manual intervention by us. The services could be made more resilient by adding the following file to supplement Plesk's service file and reloading systemd.
cat /root/reload-on-fail.conf
[Service]
Restart=on-failure
RestartSec=5scp /root/reload-on-fail.conf /usr/lib/systemd/system/plesk-php*-fpm.service.d/reload-on-fail.conf && systemctl daemon-reload
I've also made an ansible playbook for this:
https://gist.github.com/nbeernink/679b8c0bc635158b0ea4dfb96e10c7c5Additionally, you can also add this to services like nginx, mysql/mariadb, dovecot and postfix and they will restart on failure as well.
However instead of us all running these playbooks on old and new servers,…
2 votesAvailable since Plesk Obsidian: https://docs.plesk.com/release-notes/obsidian/change-log/#18-preview11
— rk
-
Add ECC CSR support
Now Plesk uses RSA encryption method, but we would like to use ECC CSR support as it's considered more modern.
2 votesWe’ve released Let’s Encrypt Extension 2.7.2: https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt
2.7.2 (17 January 2019)
• [*] In Plesk for Linux 17.8 and later, the extension now supports issuing ECDSA certificates. To have the extension issue certificates signed with ECDSA, add the following lines to the panel.ini file:
[ext-letsencrypt]
key-algorithm = ECDSA
ecdsa-curve-name = prime256v1 ; can be omitted
—
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 -
Plesk API - support for Wordpress cloning
I suggest creating an option to use Plesk API for cloning a Wordpress installation. This is well easy now in GUI environment but does not support third-party dashboard integration.
It would be great to implement this into Plesk API so clients would be able to create staging environment on one click without a need to login to the Plesk interface.
19 votesWPT 4.6 introduces the ability to clone WordPress sites via CLI (command: plesk ext wp-toolkit —clone). If you have any feedback on how this feature works, please let us know on our forum (https://talk.plesk.com)
—AK
-
Plesk Let's Encrypt and support for ECDSA certificates
As you probably know, Let's Encrypt supports ECDSA certificates. Shorter handshake time, fewer data to transfer, faster page load time in the result.
I suggest Plesk feature - add option choose between RSA and ECDSA certificate when signing with Let's Encrypt.
Best regards, Mike
24 votes2.7.2 (17 January 2019)
• [*] In Plesk for Linux 17.8 and later, the extension now supports issuing ECDSA certificates. To have the extension issue certificates signed with ECDSA, add the following lines to the panel.ini file:[ext-letsencrypt]
key-algorithm = ECDSA
ecdsa-curve-name = prime256v1 ; can be omittedIf you have any feedback let’s discuss it on our forum: https://talk.plesk.com/threads/lets-encrypt-extension.336954/
-
Allow both HTTP and HTTPS version of websites to be forwarded. It's 2018, this is vital.
This is all about security, it's simply not a fully developed product without this facility and I am hugely shocked and surprised it doesn't already exist.
27 votesThis feature is available since many years. Please accept our apologies that this feature request has not been updated when SSL for forwarding domains was introduced.
-- PD
- Don't see your idea?