Anonymous
My feedback
6 results found
-
451 votesAnonymous
supported this idea
·
-
511 votesAnonymous
supported this idea
·
-
558 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…
Anonymous
supported this idea
·
-
581 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
Anonymous
supported this idea
·
-
1,219 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
806 votes
Would you mind to try Nginx caching in Plesk Onyx 17.8 Preview?
This would be very helpful to get your experienced feedback here http://www.surveygizmo.com/s3/4165754/Plesk-17-8-Preview
An error occurred while saving the comment Anonymous
commented
Vote +1
Anonymous
supported this idea
·
ClamAV is needed into Plesk!