Anonymous
My feedback
-
35 votesAnonymous
supported this idea
·
-
169 votes
Thank 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.
— ES
Anonymous
supported this idea
·
-
1,546 votes
We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
—
AAAnonymous
supported this idea
·
-
18 votes
We consider to include DNSSEC into webhost and webpro license types. For all other types of licenses it will remain as a feature to be purchased separately.
—
ETAn error occurred while saving the comment Anonymous
shared this idea
·
-
28 votesAnonymous
supported this idea
·
-
515 votes
We have serious doubts this function can really increase server security:
1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.
As for concerns that default password requirement is set in “weak”, that fail2ban module is not…
Anonymous
supported this idea
·
-
44 votes
Thank 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.
— ES
Anonymous
supported this idea
·
-
11 votes
Thank you for your input! We will consider functionality to implement ability to set TLS as required for email connections in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
Please note that STARTSSL is a service of StartCom and there are issues with them to stay in CA role http://www.pcworld.com/article/3129725/certificate-policy-violations-force-reform-at-startcom-and-wosign.html so STARTSSL support will not be implemented in Plesk.
—
ETAnonymous
shared this idea
·
-
22 votesAnonymous
supported this idea
·
-
49 votes
While we wish it as much as you do, this is not possible to deliver Docker at customer level at the moment as customers can gain root-level access through the Docker CT and it will be an ultimate security breach.
The only generic way to deliver such function is wrapping all containers of a customer into a sort of VM similarly to Kubernetes “pods”, but Plesk itself runs in VM commonly and cannot produce extra tier of VMs. So we are very much limited by Docker itself and we are exploring how we can overcome it.
If you wish to continue conversation, please join talk.plesk.com
Thank youAnonymous
supported this idea
·
-
7 votes
By default Plesk offer webmail service for each email account. Email user can easily change his password in webmail settings.
But anyway, thank you for your input! We will consider this functionality in case that Plesk no offer webmail in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGAnonymous
supported this idea
·
-
9 votes
Thank 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.
— ES
Anonymous
supported this idea
·
-
140 votes
Thank 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.— rk
Anonymous
supported this idea
·
-
267 votes
Thank 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.
—
ETAnonymous
shared this idea
·
-
410 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Anonymous
supported this idea
·
-
476 votesopen discussion · 21 comments · Feature Suggestions » Panel/Mail · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
398 votes
Thank 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.
—
IGAnonymous
supported this idea
·
-
404 votesAnonymous
supported this idea
·
-
655 votesAnonymous
supported this idea
·
-
1,019 votes
Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.
Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:
#1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)
#2. Backup to different storages (like daily to FTP and monthly to Google Drive)
#3. Multiple Storages of the same type (like 2 different FTP servers)
ID in our Issue Tracker: PPM-1701
-DLAnonymous
supported this idea
·
@plesk I would love it if you would add it to the "higher" licences