Robin
My feedback
11 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.
—
IGAn error occurred while saving the comment Robin
supported this idea
·
-
106 votes
An error occurred while saving the comment Robin
commented
5 years and still no TLS for MySQL.
Hello?Robin
supported this idea
·
-
363 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
Robin
supported this idea
·
-
532 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…
Robin
supported this idea
·
-
1,059 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
-DLRobin
supported this idea
·
-
45 votesRobin
supported this idea
·
-
124 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
An error occurred while saving the comment Robin
commented
Feature is much needed. We need to be able to secure a webmail even when the domain is not hosted on the server, or when the web hosting is disabled. We need as well, in Obsidian, to be able to generate an email server only certificate.
This request is quite related to https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/18989752-ssl-cert-for-a-domain-frame-forwarder
If you allow generating a certificate for frame forwarder domains, then it should resolve this issue as well.Plesk, we're not in 1999, SSL/TLS should be anywhere, whenever possible... We're paying premium, then please, serve premium service.
Robin
supported this idea
·
-
23 votes
This is a valid request, for example when a provider does not want to offer free certificates to some customers. 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.
-- PD
Robin
supported this idea
·
-
41 votesRobin
supported this idea
·
-
18 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.Robin
supported this idea
·
-
12 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.
—
IGRobin
shared this idea
·
This KB article talks about Plesk's limitation here:
https://support.plesk.com/hc/en-us/articles/360014490834-How-to-change-default-charset-from-utf8-unicode-ci-to-utf8mb4-unicode-ci-in-MySQL-in-Plesk-for-Linux-
By defaults, collation is "utf8" which is "utf8bm3" which is very very obsolete.
Plesk should now use utf8mb4_unicode_ci at least, or utf8mb4_unicode_520_ci when supported.