eightynn
My feedback
12 results found
-
451 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
— ES
An error occurred while saving the comment eightynn
supported this idea
·
-
1,148 votes
An error occurred while saving the comment eightynn
commented
+9
eightynn
supported this idea
·
-
66 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 eightynn
commented
+1
eightynn
supported this idea
·
-
1,561 votes
We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
—
AAAn error occurred while saving the comment eightynn
commented
Would be great. Plesk could sell millions of extra license's ...
eightynn
supported this idea
·
-
408 voteseightynn
supported this idea
·
-
523 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…
eightynn
supported this idea
·
-
401 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 eightynn
commented
Yes, Please!
eightynn
supported this idea
·
-
560 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
An error occurred while saving the comment eightynn
commented
Please make Memcached available
eightynn
supported this idea
·
-
773 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
eightynn
supported this idea
·
-
701 votes
As an alternative option, you can configure GeoIP protection using nginx GeoIP module https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/websites-and-domains/extended-website-management/plesk-for-linux-setting-up-ip-geolocation-for-a-website.80011/
Please let us know what you think about it.
--AA
An error occurred while saving the comment eightynn
commented
this feature is more important today than ever. i don't really understand why so few votes were made for it. :(
eightynn
supported this idea
·
-
258 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
eightynn
supported this idea
·
-
211 votes
Hi.
The first version of SNI support for Mail is available in Plesk Obsidian: https://docs.plesk.com/release-notes/obsidian/change-log/#18-rc10
You need MailEnable 10.20+ (for Windows) or Postfix 3.4+ and Dovecot (for Linux) to test it.
There are cases when it doesn’t work (e.g., if you connect to mail.domain.com it will not work, please use domain.com in connection settings of your mail client) that’s why we don’t mark it as “available”. We plan to fix these issues soon.
— rk
An error occurred while saving the comment eightynn
commented
Is this feature already released for Linux?
An error occurred while saving the comment eightynn
commented
SNI (server name indication) support in the Postfix SMTP server, the Postfix SMTP client, and in the tlsproxy(8) daemon (both server and client roles)....
eightynn
supported this idea
·
An error occurred while saving the comment eightynn
commented
+ 1
Our Clients are requestion SSL for their mail services using their own domains, too. They're threatening to cancel us and change providers.
+1 - please