Anonymous
My feedback
61 results found
-
5 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.—
IG -
281 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.
—
ETAn error occurred while saving the comment An error occurred while saving the comment Anonymous
commented
Why has this not been implemented/made available yet? Even as an extension?? - Cyber Intrusions and Cyber Security keep advancing and yet, Plesk doesn't seem to appreciate the importance of defences against DNS Cache Poisoning and preventing Man in the middle attacks.
If it's not too late already, this system will soon become unfit for purpose, due to limited security options.
Anonymous
supported this idea
·
-
217 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.
— AY
An error occurred while saving the comment Anonymous
commented
create a custom file such as main.cf.custom and then add a command to plesk's scheduler for after update completed: cp custom.file /etc/postfix/main.cf
Anonymous
supported this idea
·
-
1,572 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
·
-
1,168 votesAnonymous
supported this idea
·
-
1,051 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
·
-
526 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
·
-
489 votesAnonymous
supported this idea
·
-
435 votesAnonymous
supported this idea
·
-
427 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Anonymous
supported this idea
·
-
413 votesAnonymous
supported this idea
·
-
379 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.
— AY
Anonymous
supported this idea
·
-
531 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
·
-
379 votesAnonymous
supported this idea
·
-
380 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.
— AY
Anonymous
supported this idea
·
-
362 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
— ES
Anonymous
supported this idea
·
-
323 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.— SU
Anonymous
supported this idea
·
-
358 votes
As UserVoice staff cleaned up the most of twisted voices, I’ve returning this suggestion to open discussion.
Everyone, please continue voting for this feature if you consider it important.
—IB
Anonymous
supported this idea
·
-
268 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.
— IB
Anonymous
supported this idea
·
-
320 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.
— AY
Anonymous
supported this idea
·
This NEEDS to be supported in order to comply with some countries regulatory requirements.