Automata
My feedback
39 results found
-
8 votes
Hi,
This feature was evaluated and we are planning to implement it. Stay tuned for Plesk previews – one of them might give you early access to this feature for evaluation.
—
AAAutomata
supported this idea
·
-
11 votes
Thank you for report. We are going to implement this feature in Plesk Obsidian soon.
—
IGAutomata
supported this idea
·
-
13 votes
Hi. It’s about the feature “TLS versions and ciphers by Mozilla.” We have this in our plans.
To support version 5, we have to change the code heavily – the format of the config was changed; some services don’t support the modern TLS; also, as you mentioned, it would be quite useful to provide the ability to select the config version. That’s why there is no ETA.
— rk
Automata
supported this idea
·
-
13 votes
Hi,
We’re looking into adding this functionality in one of the upcoming releases.
—AK
Automata
supported this idea
·
-
22 votes
We’d like to introduce this feature, but we’ll have to solve certain technical difficulties first (for example, properly handle cases where database structure is updated by a plugin and you want to roll the changes back). We’re positive that we can overcome these difficulties, though.
—AK
Automata
supported this idea
·
-
25 votesAutomata
supported this idea
·
-
32 votesAutomata
supported this idea
·
-
37 votes
Thank you for your input! We will consider this functionality in upcoming releases.
We have created internal document with ID PPM-569 for your reference.
Everyone, please continue voting for this feature if you consider it important.
—
ETAutomata
supported this idea
·
-
50 votes
Thanks for your input! we consider this as a valid and clear feature request that is registered in our tracking system as PPM-2515.
There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!Automata
supported this idea
·
-
107 votes
Hello,
Thanks for your input, we understand the importance. This Feature request is registered in our tracking system as PPM-344 and it will be included into future Plesk versions. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!Automata
supported this idea
·
-
174 votes
Thank you for your input! We are planning to implement this functionality in upcoming releases. The request is registered as: PPM-2517
Everyone, please continue voting for this feature if you consider it important.
— ES
Automata
supported this idea
·
-
198 votesAutomata
supported this idea
·
-
211 votesAutomata
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
-DLAutomata
supported this idea
·
-
437 votes
An error occurred while saving the comment Automata
supported this idea
·
-
71 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
Automata
supported this idea
·
-
120 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.
—
IGAutomata
supported this idea
·
-
543 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.
—
IGAutomata
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…
Automata
supported this idea
·
-
570 votes
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
SE
Automata
supported this idea
·
+1 for me !