Currently CloudFlare ServerShield is implemented using partial (CNAME) setup. What is the point in a partial setup when you can benefit from full DNS? You get anycast DNS with CloudFlare on full DNS.

It would be great if it would be possible to create multiple users which can use the Git repository. Today only one user can access the Git repository. It is the admin user which was created during the creation of the subdomain. New created Web Users for the subdomain can not access the Git repository. It is a feature which I am missing because I wanted to host a private Git repository for our small private team.

https://talk.plesk.com/threads/can-not-create-new-users-for-local-git-repository.342409/

Currently Plesk supports Clef and Google Authenticator for Plesk admin accounts.

However if a customer creates additional user accounts (service accounts with owner rights for example) the 2FA option is not available.

We would appreciate this feature especially in combination with multi-server management, where one customer may have multiple admins and multiple domain subscriptions.

-Philipp

Same sort of thing as the Route53 extension just with Google Cloud DNS

Availability to move subscriptions between customers in Plesk Multi Server

To allow or disallow a subscription owner to use Let's Encrypt.

Since plesk supports individual Ruby, Node and PHP settings per subscription there should also be extended support for Python.

It would be a good approach to enable / disable python per subscription by allowing / disabling access to python and to setup a virtualenv per subscription so that every subscription can have different packages with different versions installed.

Bitbucket repository provides the possibility to generate SSH keys with passphrase protection for better securing.
However, Git extension in Plesk doesn't support passphrase protection and fails with "Permission denied" error.

Consider adding passphrase protection as it will increase the security.

When the DNS service is not hosted on Plesk, the Let's Encrypt wildcard certificate cannot be renewed automatically. Therefore, please provide us with a way to use our own DNS tools (API or script) to create the TXT record on our side and force the extension SSL It! to finish the issuing by itself.

Be able to revoke a let´s encrypt certificate

Described in https://tools.ietf.org/html/draft-ietf-acme-acme-06#section-8.4

The problems with mail/webmail/lists subdomains could be obsolete, because a acmechallenge.lists.domain.tld txt record could be challenged.
So no problems with webroots etc.

Now that you are adding the ability to install Nextcloud on Plesk, it would be nice if we can use it as a backup location. This way the backups can be easily synced to the computers that are connected to the account.

Prestashop toolkit extension (like wordpress and joomla)

Fail2Ban may send abuse reports to IP owners of blocked IPs.

The report should include a predefined message, the relevant part of log files, and full signature of sysadmin.

The abuse e-mail address for a IP could be automatically retrieved with a RIPE Database Query.

Offer a Jitsi deployment extension, like you do for NextCloud

Would be nice if the extension could do resets (git reset --hard) /rollbacks

I want Let's Encrypt feature to be added to the XML API

Plesk currently has many great extensions. It would be amazing if you could get the data from these extensions and generate report for customer about its website.

For example, report could include:

• Page speed optimization (Data from the Google PageSpeed Insights extension)

• SEO optimization (Data from the SEO Toolkit extension)

• Website security (data from Wordpress Toolkit, Sucuri Security Scanner, Advisor and Revisium)

• Information about updated plugins and themes (data from Wordpress Toolkit)