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
265 results found
-
Commit changes on live site to a remote git repository / version control system
I have read a lot about git integration in plesk and it sounded great,e.g. here:
https://docs.plesk.com/release-notes/onyx/whats-new/ or here https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/git-support.75824/
But actually as far as I found out, it is only possible to pull and deploy changes from a remote repository to your website. It is very disapointing that it is not possible the other way round:
I would like to make changes to my live site, and commit them (including all changes to the mySQL DB and files) and push them to my github repo.
(Why) is this not possible?
It would be perfect to make quick "backups" and revert…7 votesThank you for your input! 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.
-
Please extension availability based on condition
Currently I have noticed that extension are available to all customers or reseller. Can these be restricted based on service plan or customer wise or reseller wise. In case as hosting provider, if we don't want to give additional functionality to all customers. Extension for example, please consider let's encript
7 votes -
SSH Key authentication for Site Import
Currently "Site Import" ext only supports username and password for SSH/FTP. If the source server doesn't support password SSH auth then it is not possible to import a website via SSH. Can the SSH Key auth option be added?
6 votesThank you for your input! 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.
—
IG -
Ability to exclude www for domain aliases when issue Let's Encrypt certificate
Currently in SSL It! extension the option is "Include a "www" subdomain for the domain and each selected alias". In that way the Let's Encrypt limit will take effect if many aliases exist in Plesk for domain.
For example, it is required to protect example.com, www.example.com and 50 aliases. In that way Let's encrypt will protect example.com, www.example.com and 100 aliases (50 without www and 50 with WWW) and it will hit the Let's Encrypt Limit.
6 votes -
Ability to automatically update TXT records for Wildcard certificates through Domain Connect
The domain validation for letsencrpypt for wildcard domains uses a TXT-record (acme-challenge.<YOURDOMAIN>).
This record is set by plesk on the local dns server, but it is not synchronized to our (the official) nameservers for a domain which is using the domainconnect extension. So the validation will fail, or the customer have to set this record manually every few months, when a revalidation is required.Can domainconnect be improved to synchronize this record?
6 votesThank you for your input! 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.
—
IG -
Wildcard Certificate automatic placement for Domains
We want to place wildcard certificate for all our subdomain with wildcard and we want to make it default while creation of Domains.
It is required because we are building saas application with the help of plesk api and we offer our wildcard domain for our customers with SSL, auto ssl takes quite time to be validated but if we can include our wild card certificate and the customer can see the subdomains with SSL.
6 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 -
Allow setting a custom port for Git webhook
Allow setting a custom port for Git.
This would allow having Plesk publically blocked (port 8443) but it would still be possible to use the git web-hooks.6 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 -
Configure plesk email security settings per domain
Since we've installed Plesk Email Security it's not possible to configure all the mailboxes within a domain with a specific SpamAssassin configuration.
The only options available are per mailbox or server-wide which lacks of functionality when we've more than 100 mailboxes on a domain.
6 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 ability to manage DNSBL in Plesk Email Security Extension
It would be great to add ability to manage DNSBL settings in Plesk Email Security Extension because:
1. The default settings can be not too strict for client needs;
2. No way to add IPs or domain into the settings I need to improve mail server security;6 votesThank you for your input. 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.
—
IG -
Allow sending/receiving mails for address of Public Mail folder
In Plesk Premium EMail it is not possible to send or receive mails on the address of the public mail folder's name.
It should be possible to send mails from the public mail folder and mails received in it should be visible for other mail-users as in Microsoft Exchange.
6 votes -
Enable advanced monitor for customers
Enable advanced monitor for customers in order to be able to see the performance of the server.
6 votesThank you for your input! 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.
— AY
-
The ability to clone WordPress multisite
WordPress Toolkit Clone feature also available for in supports WordPress multisite.
6 votesIn WP Multisite installations you have one single WP controlling many different websites and domains. "Cloning" a multisite installation seems to be a challenge, because when you clone a site, you need to mention a target where to clone the site to (a new URL, a new subdomain). As a multisite installation has many URLs, it seems impossible to clone these to one single domain. It will be unclear which domain is actually cloned or how to map source to target.
But as always, we're open for ideas and would love to hear more details from you how you imagine the workflow. Please describe in your comments what you expect to happen when you clone a multisite installation, e.g. how you'd want to map source to target(s). Would you for example want to see a dialog where you can enter new domains and subdomains for each existing URL in the…
-
Add color support for comments in panel.ini editor extension
There's no comment color support, which causes visual bugs in the panel.ini editor view.
For example:
A word in the default description for the [pmm] section has a tilde character ( ` ) instead of an apostrophe. This causes everything after it, including other sections, to appear in brown color, and not the correct color code for further sections.Comments should be recognized as such and have their own color code (like gray) so its contents don't take over the color in upcoming sections. It can confuse users.
5 votes -
5 votes
This 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
-
Grafana - Editing charts
It'd be great to have an option to permanently alter the grafana's charts properties(colors, etc.)
5 votes -
Enable/Disable Route 53 per domain/reseller
Since Route 53 is a paid service, it would be good to be able to enable/disable the extension for specific domains/customer/resellers instead of just for the whole server.
5 votesThank you for your input! 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.
—
IG -
Option to add own Grafana dashboards to advanced monitoring
You can already achieve this by editing the predefined dashboards in Grafana. But this isn't a very pretty solution for this, it would be nicer with the option to add full dashboards.
5 votes -
Let's Encrypt Notifications management on per Domain basis
It would be nice to be able to manage Let's Encrypt Notifications on per domain basis.
Right now, the notifications can be managed sort of by role. Administrator, Reseller or Customer thus the notifications are enabled for everyone or disabled for everyone as well. More information here: https://support.plesk.com/hc/en-us/articles/360001371114
Such scenario is not suitable when the notifications are to be received globally but some customers just don't want to receive them.
Thanks in advance.
5 votesThank you for your input! 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.
—
IG -
Add warning to Docker extension that container will be reachable form the outside by default
By default Docker container is available from the outside and Plesk users sometimes are unaware of it. Sometimes Docker container is used only locally.
Suggestion is to add a warning about this or add a check box to close remote access on creation.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 -
Searching interface for Plesk Email Security that shows the information about the sender (IP addresses etc)
There are currently no interfaces or logs for Plesk Email Security that show who messages are being received from (including IP addresses). in case most of the spam received on server are from several IP ranges, it would be convenient to search and block specific IP ranges.
Please implement the web Interface that allows to search by the following parameters:
Recipient: *@example.com
Subject:
Status: Regular Email | Spam | Any
IP:Then the search results would show:
Email Address, Subject Line, From Address, From IP, From Hostname5 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?