Necesitamos poder trabajar con MAGENTO

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

Bring your Mattermost version up to date so that all features work on the Mattermost Android app and the app stops throwing a warning that the server version is out of date and not supported.

Disable root access for the SSH Terminal extension only for additional admin users

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.

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.

servershield by cloudflare is very essential for some users.. so plz add extension servershield by cloudflare

is mostly recommended by wordpress

Often the new versions of Nextcloud are not compatible with some plugins, so an option to select the major version to be installed would be useful

Prestashop installer version 1.7.5.x could be added. I have Plesk Onyx 17.8.11 and in a previous version there was the installer of thePrestashop 1.7.x, plesk 17.8.11 it does not appear. If there is a installer, the prestashop updates can now be done from the prestashop itself

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.

Ability to add/upload additional/custom SpamAssassin files (.cf) inside Plesk Email Security extension. It will increase the spam security level.

For example
1. some servers with the same service plans created.
2. Service plan on one server changed
3. Service plan on other servers can be updated using a service plan from the source server.

Cloudflare dropped support for Cloudflare extension. Please consider native integration with Cloudflare. It is required for example to automatically update Cloudflare IP addresses with Nginx configuration to show real IP: https://support.cloudflare.com/hc/en-us/articles/200170786-Restoring-original-visitor-IPs-Logging-visitor-IP-addresses-with-mod-cloudflare-

System time is one thing on the OS. It should remain free to be set to whatever Timezone the System Administrator need it.

Having Plesk requesting to change System Time or my device Timezone is absolutely not acceptable.

• Imagine all software ask the same ?
• And what if I travel and my device change Timezone ?

Plesk should avoid imposing to set System Time to have Google Authenticator Working.

Plesk team must improve its implementation of Google Authenticator.

The Plesk Email Security Extension is a really good way to secure the mailservive in Plesk.

And you have a nice graph where you can see, how many spam mails you recieve and send.

But one thing is missing... If our server identifies a mail as spam, we want see which mail it was and not only a summary how many spammails the server sends.

It should be possible to switch the antivirus in Plesk Email Security extension between DrWeb and ClamAV or both running simultaneously while quarantined mails remains available in any combinations.

Why is there a selection for the encoding in the text-editor (where it makes no sense in my opinion) and none in the code editor, where it would make more sense?

Please add it.

Error details from "Could not issue/renew Let`s Encrypt certificates" notification are too verbose and excessive. For example:

• 'Lets Encrypt example.com' [days to expire: 19] [-] example.com

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/1654356342.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403

Detail: Invalid response from http://example.com/.well-known/acme-challenge/5hml56m8-22VgeVZQPRjBUTGP6UFTYXoN7ZiDdQntrI [1.2.3.4]: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"

the following would be enough:

Detail: Invalid response from http://example.com/.well-known/acme-challenge/5hml56m8-22VgeVZQPRjBUTGP6UFTYXoN7ZiDdQntrI [1.2.3.4]: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"