Robin Labadie
My feedback
18 results found
-
385 votes
In Plesk Obsidian 18.0.54, published July 18th, 2023, the ability to tune the MySQL/MariaDB server performance was added to Tools & Settings > Performance Booster (under “General Settings”).
Please try it and let us know here what further improvements you would like to see.
-- PD
An error occurred while saving the comment -
13 votes
-
8 votes
-
556 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…
An error occurred while saving the comment "We have serious doubts this function can really increase server security"
Well, I have serious doubts about Plesk's conception of security regarding logins.With or without anti bruteforce, having a different username than default is always a security improvement.
-
378 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
An error occurred while saving the comment Totally needed in order to have a custom URL for custom webmails.
-
51 votes
Thank you for your input! We will consider this functionality for the upcoming releases if it becomes popular enough.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
219 votes
-
219 votes
-
242 votes
-
394 votes
This is a valid request, so we’ll look into it. 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.
The original request contains a manual solution, so, we consider to automate it. Please, add a comment if your case will not be solved with that solution.
Thanks in advance!
— rk
-
129 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 -
583 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 -
52 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.
The previous status update was done by mistake.
— AY
-
49 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.
As workaround you can use this KB article https://support.plesk.com/hc/en-us/articles/360002886854-Is-it-possible-to-create-scheduled-backup-tasks-via-CLI-API-
—
IG -
510 votes
An error occurred while saving the comment It would be great to be able to have diifferent mailbox quotas as well. Say if a customer wants one 1GB mailbox and one 10GB mailbox. Currently, customers have control on the mailbox value, being limited by the max mailbox size therefore we cannot sell differently sized mailboxes.
@Lars & @Anonymous
Not even needed to symlink, you can just use a mount point in your fstab for that. :)
-
20 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 Thanks to Plesk support for adding this uservoice entry.
Another use case is to simply manage two domains at once in different tabs. Say you want to change PHP version (or any other setting) for 5 domains, it would be way easier and way faster to open those 5 domains from the domain list and to make the change on each tab, rather than going back to the domain list (or searching the domain) for every single change.
PS: My initial input about this:
After a few years using Plesk, I'm getting more and more tired of not being able to open multiple tabs, especially when doing similar actions on multiple domains, it would save a lot of time to be able to open multiple tabs, just like most web applications. -
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 I would have bet this was possible at some point.
Plesk doc even mentions it there, but I guess this was relating Customer settings and not mailbox user settings: http://docs.plesk.com/en-US/onyx/administrator-guide/mail/antispam-tools/spamassassin-spam-filter.59432#switching-on-spamassassin -
30 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
I do see the feature (Debian 11/MariaDB 10.6.14, no Nginx), but no MySQL settings are available.
Edit: My bad, auto update didn't happen, I was still in 18.0.53 😅
Would be great if:
- More settings were available
- We could selectively activate some optimizations and not others
- We could customize settings values from Plesk interface, but still see the recommended value
- Added information boxes in order to explain what the value does and what are the risks (for example, innodb_flush_method = O_DIRECT_NO_FSYNC will go bad when using XFS)