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
127 results found
-
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-breakdownRotating 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)…
3 votesThank 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
-
Oversign Emails' DKIM From, To, and CC headers
As in:
https://proton.me/blog/dkim-replay-attack-breakdownOversign 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 votesThank 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
-
Ability to disable aum automatic updates in mod security and apply it manually
Provide the ability to disable aum
automatic updates in mod security and apply it manually2 votes -
Add option to mitigate known vulnerabilities by default during installation of WordPress
There is an option in WP Toolkit to mitigate the Unauth. Blind SSRF vulnerability. However, this may only be applied only once WordPress has already been installed. Please add possibility to secure the instance in this regard (and any other vulnerabilities that might be found later, if such option is added to WP Toolkit) directly when installing WordPress.
2 votes -
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 voteThank 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
-
Improve Plesk Country Firewall Usability
Plesk Country Firewall
1) Add a check for duplicate country abbreviations on save.
2) (x) add checkbox to sort alphabetically
3) Add a drop down to select the country. Currently you have to look up the country 2 digit code. So add a drop down to select country then add the 2 digit abbreviation.1 voteMost ISO codes of rogue nations are well known. We think that changes to geo IP blocking are rarely needed. To keep development costs reasonably low, perfect comfort for rarely used features is not a priority. In a server's lifetime it may occur twice that this is changed, so we wonder how often this feature is used in your daily routine that the added comfort is required? Please comment how you determine the countries to be blocked and why you change countries often so that we understand your routine better and can provide a better product while trying to keep license prices low.
-
Block IP address ranges of cloud services (AWS, Google, DigitalOcean)
Be able to block IP address ranges of cloud services (e.g. AWS, Google, DigitalOcean) via Plesk Firewall to avoid junk traffic and hacking attempts.
At the moment, it is only possible to block IP addresses by countries1 vote -
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 votesThank you for your idea! We will consider this functionality in upcoming releases.
-- PD
-
Add rate-limiting rules to Fail2Ban
Please implement a rule for rate-limiting requests from outside resources and include it into Fail2Ban's default ruleset.
5 votes -
Add configuration option for protection against host header injection
It will be good to add the feature to configuration the Plesk host header injection protection.
Curretly that is not possible to make it by the Plesk interface.1 vote -
SSL Certificates with passphrase
It'd be great to have an option to upload 3rd-party SSL certificates with passphrase in Plesk
2 votes -
Deprecate clear domain names as home directory
Since plesk is storing each vhost as clear domain name, every user wit shell access is able to see which domains/customers are on this host, eg. with > getenv passwd
We know we can chroot the user but chroot is NOT a security feature and makes trouble with applications the user might expect (or the environment these applications expect) - and there is still a way to break out from the environment or new ways get discovered. Much afford for nothing in the end.
We do not want to put customers in containers, jails whatsoever to restrict the user access…
1 voteThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
Thanks in advance!
--
IG
-
Firewall, Remote Adress(es): input a lot of remote adresses at once.
In the Firewall settings, to input remote adress(es) to block or allow, it would be usefull, to input a lot of remote adresses, just to block or allow a whole company at once (after getting their adresses from ipinfo.io, for example).
Actually I get spam, check remote IP (at dnslytics.com for example) and block that IP, if wanted.
After getting a lot of these mails from IP adresses of the same company, I get the IP adresses from that company and block all the known IP ranges...one by one.
That could be 100s or more and take too much time.…2 votesThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
Thanks in advance!
--
IG
-
Ability to monitor clients uploads via FTP or File Manager
It would be nice to have the ability to detect customer uploads via FTP or File Manager. So it will be possible to check files afterwards.
2 votesThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
Thanks in advance!
--
IG
-
Iptables: Allow Rules via the shell
Our Intrusion prevention system CrowdSec adds one rule having a blacklist to Ipables.
If you manipulate the rules in the UI, Plesk rewrites all rules. Therefore manually added rules are no more available.
This could be fixed very simple by having an additional script, which will be called after saving the rules by the UI.
3 votes -
Create security.txt
Help admins and customers to create a security.txt file when creating a site in Plesk Panel, see https://securitytxt.org/
No details yet.1 vote -
Add support to Atomicorp rulesets for ModSecurity 3.0 (nginx)
At the moment you can only choose the OWASP ruleset in the Plesk UI for ModSecurity 3 (nginx). Please add support to Atomicorp rulesets as well.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Manage all Firewall rules via Plesk GUI on Plesk for Windows
Ability to manage Windows Firewall rules not added by Plesk. I.e., the rule added by MySQL installer
5 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
add option to preload hsts
can you add the option to the hsts switch to add preload option?
i have to disable the hsts switch and manual add this option to the Nginx directive as so
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload";
9 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Add Plesk password generate button to the Create user for the protected directory form
Add a Plesk password generate button that matches with the server password policy level in the Create user for the protected directory form
2 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
- Don't see your idea?