My feedback

1. Change admin username

   502 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   66 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →

   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminSergey L (CTO, 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 enabled by default or may consume extra resources, etc – they are much irrelevant here. If someone is not willing investing some time into setting better password, into changing password policy or into installing/enabling server protection – changed admin name will again be only a false sense of security. If a password is “1234567”, then login doesn’t really matter.

   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… more

   Jay Smith supported this idea  ·  Jul 12, 2014

2. Fix File and Folder Permissions for docroot from Plesk UI

   51 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Feature Suggestions » Web / HTTP functions  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →

   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   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  ·  Jul 12, 2014
   An error occurred while saving the comment
   Jay Smith commented  ·  Jul 12, 2014  ·  Edit…  ·  Delete…

   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.

   Save Submitting...