Jay Smith
My feedback
-
154 votes
Thank you for your input. We will review this nginx module to see if we should support it out of the box
Jay Smith
supported this idea
·
-
323 votesopen discussion ·
AdminSergey L
(Director of Program Management, Plesk International GmbH)
responded
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…
Jay Smith
supported this idea
·
-
41 votes
Looks like “plesk repair fs” can help: https://docs.plesk.com/en-US/12.5/administrator-guide/plesk-administration/plesk-repair-utility/plesk-repair-utility-file-system.75675/
Everyone, please continue voting for this feature if you consider it important!
— rk
Jay Smith
supported this idea
·
-
1,062 votes
Hi everyone, we’re working on UI for this feature and we would like to kindly ask you to answer one more short survey for better understanding your needs and priorities :) your answers are very important, thank you in advance!
https://pleskteam.typeform.com/to/r7WjG8
— ZB
Jay Smith
shared this idea
·
This can also be extended to when the domain is switched from the FastCGI PHP module to the Apache module, where the tool would chown the domain's web document root to apache:apache.