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
- or
No existing idea results
- ~ No ideas found ~
2080 results found
-
Please upgrade mysql version on plesk dashboard
Currently not supported latest most of the features due to sql query getting large and not able to use fully supported features to speed up website.
1 vote -
Implement a generic ACME client for TLS Certificate issuance and automatic renewal
The runtime for certificates is being reduced soon making manual renewal impossible.
From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days.
As of March 15, 2026, the maximum lifetime for a TLS certificate will be 200 days.
As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.
As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.
Currently the ONLY way to automate certificate renewal in Plesk is by using the Let's Encrypt extension using the official Let's Encrypt ACME servers.
The other extensions for generating certificates via Sectigo etc do not allow automatic renewals.Many CAs now offer their own ACME servers for automatic renewal of their certificate offerings, but Plesk offers no way of making use of them.
Please implement the ability to use arbitrary ACME back-ends for use on all CAs and not just Let`s Encrypt.This is extremely important and should be implemented in Plesk within the next 12 or so months.
Thank you very much
The runtime for certificates is being reduced soon making manual renewal impossible.
From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days.
As of March 15, 2026, the maximum lifetime for a TLS certificate will be 200 days.
As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.
As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.
Currently the ONLY way to automate certificate renewal in Plesk is by using the Let's Encrypt extension using the official Let's Encrypt ACME servers.…1 vote -
Expert Heat Pump Installation Auckland – Airperfection
Looking for reliable heat pump installation Auckland services? Look no further than Airperfection – your local experts in heating and cooling solutions. Whether you're upgrading your current system or installing a brand-new heat pump, we provide fast, efficient, and affordable services tailored to your needs.
At Airperfection, we understand Auckland’s changing climate and offer energy-efficient heat pump systems to keep your home or business comfortable all year round. Our team of certified technicians ensures a smooth and professional installation process with minimal disruption.
Why choose Airperfection for your heat pump installation in Auckland?
Trusted local experts with years of experience
Top-quality brands and systems
Competitive pricing with no hidden costs
Clean, safe, and efficient installations
Excellent customer service and aftercare support
Don’t settle for less when it comes to comfort. Choose Airperfection for the best heat pump installation Auckland has to offer. Contact us today for a free consultation and quote!
visit for more information https://airperfection.co.nz/services/heat-pump-installation-auckland/Looking for reliable heat pump installation Auckland services? Look no further than Airperfection – your local experts in heating and cooling solutions. Whether you're upgrading your current system or installing a brand-new heat pump, we provide fast, efficient, and affordable services tailored to your needs.
At Airperfection, we understand Auckland’s changing climate and offer energy-efficient heat pump systems to keep your home or business comfortable all year round. Our team of certified technicians ensures a smooth and professional installation process with minimal disruption.
Why choose Airperfection for your heat pump installation in Auckland?
Trusted local experts with years of experience
…
1 vote -
Roundcube Sieve Autoresponder missing DKIM signature
In the current implementation, sieves autoresponder is using an empty sender address for auto reply.
We suggest the following config change:
/etc/dovecot/conf.d/90-plesk-sieve.confplugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve # Horde webmail (Ingo sieve backend) is not aware of RFC 'imap4flags' and # 'enotify' extensions. Enable old deprecated ones. sieve_extensions = +notify +imapflags sieve_vacation_send_from_recipient = "yes" # <- New }This setting ensure that the original recipient is used as envelope sender address for the auto reply, especially required for big providers like google and microsoft. This setting also enables DKIM signing for auto responder to be compliant with SPF / DKIM and DMARC policies.
In the current implementation, sieves autoresponder is using an empty sender address for auto reply.
We suggest the following config change:
/etc/dovecot/conf.d/90-plesk-sieve.confplugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve # Horde webmail (Ingo sieve backend) is not aware of RFC 'imap4flags' and # 'enotify' extensions. Enable old deprecated ones. sieve_extensions = +notify +imapflags sieve_vacation_send_from_recipient = "yes" # <- New }This setting ensure that the original recipient is used as envelope sender address for the auto reply, especially required for big providers like google and microsoft. This setting also enables DKIM signing for auto responder to be compliant…
1 vote -
Composer tool enhancements - add GUI command interface and private repository support
In my opinion the plesk composer utility needs some of the functionality that the laravel composer tool has:
Ability to run composer commands from the GUI rather than the CLI like the Laravel tool has implemented - if the site/subscription is not a laravel application, you don't have this option. You must use the CLI.
Ability to require private repositories - much like the git utility does for cloning a repository. Currently we have to manually edit the composer.json file then either add the users default key to github as a deploy key or generate individual keys for each repository if multiple private repos are needed (github does not support using the same deploy key over multiple repositories)
on the flip side, the Laravel tool could use the same functionality to include private repositories and also a manual editor for the composer.json - again if you have Laravel toolkit installed and no composer extension ... you can't edit the composer.json from the GUI.
In my opinion the plesk composer utility needs some of the functionality that the laravel composer tool has:
Ability to run composer commands from the GUI rather than the CLI like the Laravel tool has implemented - if the site/subscription is not a laravel application, you don't have this option. You must use the CLI.
Ability to require private repositories - much like the git utility does for cloning a repository. Currently we have to manually edit the composer.json file then either add the users default key to github as a deploy key or generate individual keys for each repository…
1 vote -
Smart Email Log Dashboard
Currently, Plesk only allows a raw, line-by-line view of mail logs through tools like Mail Log Browser. However, there is no real centralized and user-friendly interface that enables users to easily and clearly review the history of sent and received emails on the server.
The idea is to provide a global dashboard that groups together all domains and all existing mailboxes, offering a clear and organized chronological view of messages handled by the server. Each row would represent a single message (incoming or outgoing), with the main information immediately visible: sender, recipient, delivery status, spam score, date and time, and email subject.
Using advanced filters, it should be possible to narrow down the view by domain, by individual mailbox, or by groups of mailboxes, making both detailed and high-level monitoring easier. By clicking on a message, users would access more technical details, such as the sender’s or recipient’s IP address, the Message-ID, any SMTP error codes, and a full description of the error in case of delivery failure.
A tool like this would be extremely valuable for both system administrators and clients, simplifying the identification of delivery issues and improving transparency and control over email communications. It would represent a major improvement over the current basic log view, delivering a much more modern and efficient user experience.
Currently, Plesk only allows a raw, line-by-line view of mail logs through tools like Mail Log Browser. However, there is no real centralized and user-friendly interface that enables users to easily and clearly review the history of sent and received emails on the server.
The idea is to provide a global dashboard that groups together all domains and all existing mailboxes, offering a clear and organized chronological view of messages handled by the server. Each row would represent a single message (incoming or outgoing), with the main information immediately visible: sender, recipient, delivery status, spam score,…
1 vote -
Root level File Browser and File Editor
Full file browser, like the customers use at their website but for the entire server, so the admin can easily required modify files.
1 vote -
Disable custom Service Plans for Reseller
I genuenly need the option to disable the creation of Service Plans on the Reseller level. So all Service Plans (or selected) from the Admin will be available for the reseller to choose from.
Background:
As an Admin I would like to define the service packages, so the Reseller can Choose from the service packages for new users / domains but cannot create or edit them.
So I can have Resellers which can build Websites and manage Customers ontop of my existing pricing structure.Thanks for your Votes and the Implementation.
1 vote -
Add the amount of banned IPs to the IP Address Banning (Fail2Ban) page. Not just on the home screen.
When I am in the screen for Tools & Settings / IP Address Banning screen, it would be helpful to see the number of banned IPs in the top of the screen of the "Banned IPs" tab. Instead of only seeing the list of IPs that are banned and amount amount of pages worth. This seems really simple, but for me it would be effective to quickly see at a glance how many IPs are actually being banned at any given time. This would be a great feature for the newest update of Plesk Obsidian. I am using the WebPro version.
Jeff :)
When I am in the screen for Tools & Settings / IP Address Banning screen, it would be helpful to see the number of banned IPs in the top of the screen of the "Banned IPs" tab. Instead of only seeing the list of IPs that are banned and amount amount of pages worth. This seems really simple, but for me it would be effective to quickly see at a glance how many IPs are actually being banned at any given time. This would be a great feature for the newest update of Plesk Obsidian. I am using the WebPro…
1 vote -
Show LetsEncrypt certificate expiration date in certificate management
As LetsEncrypt keeps on telling me to renew my certificates and plesk tells me that it automatically renew's 30 days before expiration, it would be handy to actually SEE the expiration date in the Certificates overview under Tools&Settings -> SSL/TLS Certificates directly in the list view and also in the detail view of the certificate, if you click on one certificate.
1 vote -
add read-only API access
Especially for automatically executed scripts that use the XML or REST API, it would be much more safe and secure to have read-only credentials.
For instance, for a script that automatically publishes the current list of sites on our intranet, and a script that uses what's in Plesk for automatic billing, we really don't want to store credentials with them that allow them (or anyone who steals those credentials), to change anything (e.g. delete everything).
This requires the creation of a new type of attribute on users or authentication tokens: read-only.
Ready-only users or tokens can be used to make API calls, but all of their calls that would modify anything will be rejected with an error response with status 401 or 405.
Especially for automatically executed scripts that use the XML or REST API, it would be much more safe and secure to have read-only credentials.
For instance, for a script that automatically publishes the current list of sites on our intranet, and a script that uses what's in Plesk for automatic billing, we really don't want to store credentials with them that allow them (or anyone who steals those credentials), to change anything (e.g. delete everything).
This requires the creation of a new type of attribute on users or authentication tokens: read-only.
Ready-only users or tokens can be used to make…
1 vote -
reject email when dkim is missing
Add the ability to configure Plesk to reject all incoming emails that have no DKIM.
In other words, when email comes with DKIM Feed: No signature1 vote -
Automatically Disable Maintenance mode
It would be nice to make it possible to automatically disable maintenance mode if a timer is connected (like a checkmark to disable maintenance mode when timer expired).
We quite often want clients to publish their sites early in the morning (5am/6am) and have to set an alarm outselves, wake up at night, just to disable the maintenance mode.
We always put a count down timer when the website goes online. It would be nice if once the timer is finished the maintenance mode would get disabled so we wouldn't have to do this manually.
1 vote -
add a general rate limit option for service connections in iptables
Similar, but not the same as proposed in https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/46431970-add-rate-limiting-rules-to-fail2ban
Problem:
Scrapers and bad bots are reacting to an increased propagation of Fail2Ban bad bot rules. Their new tactic is to collect a number of domains hosted on the same ip address first, then to send burst style requests to all these domains "at once" so that they get a response before Fail2Ban rules kick in to ban the ip address of the requestor. Since 3/2025 in some cases it has been observed that these attack style bursts can be so massive that they drive up the cpu usage of a server to a point where it becomes unresponsive for minutes (5+ ... 30+) until it is able to process all the requests.Solution:
A general rate-limiting for iptables. Add a rule in position (1) of iptables that limits the number of new connections from the same IP address, for example# iptables -I INPUT 1 -p tcp --syn -m multiport --dports 80,443,8443,8447 -m connlimit --connlimit-above 30 --connlimit-mask 32 -j REJECT --reject-with tcp-reset
A feature in Plesk that could do this could do two things: For one it should be possible to add several entries to the top of iptables for different ports (dports parameter). For some users it will be important to also limit the rate of incoming connections to other ports such as 3306 but with a different connlimit. As the connlimit should be different for different services, it will be important to being able to add several such entries (like in the Firewall module you can add different rules for different services).
Second, the feature will need the connlimit number user configurable, because this strongly depends on how the server is used. VPS users will want to have a low number, users with a server mainly for their own office work will want to have a high number and virtual webhosting resellers will want to have a middle number like 50 etc., because the number of connections made depends on the usage scenario, and we don't want to block legitimate users.
Finally, this needs to become part of Plesk, because users won't want to set the rules themselves after each server restart, so they should be an integral part of what Plesk sets in iptables after a server restart.
Similar, but not the same as proposed in https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/46431970-add-rate-limiting-rules-to-fail2ban
Problem:
Scrapers and bad bots are reacting to an increased propagation of Fail2Ban bad bot rules. Their new tactic is to collect a number of domains hosted on the same ip address first, then to send burst style requests to all these domains "at once" so that they get a response before Fail2Ban rules kick in to ban the ip address of the requestor. Since 3/2025 in some cases it has been observed that these attack style bursts can be so massive that they drive up the cpu usage…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!
-- SH
-
Synapse Matrix with Element and Synapse Admin incl. coturn etc..
Synapse Admin with Element Web and Synapse Admin incl. coturn and User regestration .
1 vote -
External Links inside Plesk CP
Open all external links from inside Plesk CP with new tab. Currently only about half of these links open in new tab and it's a PIA when they don't.
1 vote -
Add NSEC3 option for DNSSEC (prevent zone enumeration)
Please add an option in DNSSEC configuration to use NSEC3.
NSEC3 does not allow DNS zone enumeration like NSEC.Documentation :
https://bind9.readthedocs.io/en/v9.18.14/dnssec-guide.html#nsec-or-nsec3Regards,
Laurent.1 vote -
Custom timeframe for outgoing mail limit (e.g per minute, per 5 minute and etc.)
Custom timeframe for outgoing mail limit instead of default hour rate(e.g per minute, per 5 minute and etc.)
1 vote -
Mail Folder autoclean after x day
Hello we search a solution, to autoclean / autoremove mail folder after x day's
Like this plugin https://bitbucket.org/Black75/autoclean/src/master/
"Autoclean is a Roundcube plugin, that allows the user to configure automatic cleaning of old messages from folders."1 voteThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
In the meantime, I can suggest checking the workaround from the following article:
-- SH
-
Ability to remove plesk.page temporary domain from server
Would be great to let an user completely delete all occurrencies of plesk.page temporary domain from a server or at least explain how to remove that.
Every temporary domain created, also the default assigned as hostname, leave a persistent trace as after deletion A records still show up and point to server IP.
1 vote
- Don't see your idea?