Anonymous
My feedback
-
28 votesopen discussion · 4 comments · Feature Suggestions » Extensions · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
51 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
Anonymous
supported this idea
·
-
132 votes
Thank you for your input! We will consider these nginx configuration suggestions in upcoming releases if it will be popular.
Everyone, please continue voting for this feature and add your comments if you consider it important.
—
IGAnonymous
supported this idea
·
-
217 votes
Current scope for Plesk Onyx is to enable an ability to serve all http(s) requests by Nginx only.
Note: apache will still be installed. Switching of apache to optional component is subject for the next release.
Update:
The ability to turn off Apache and have content served by nginx only on a per-website basis is now available in the latest Plesk Onyx 17.0.14 preview. We encourage you to check the implementation and let us know what you think. Please visit the following forum thread to learn how to access the preview: https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172
How to try this feature:
Go to any website, click Apache & nginx Settings and deselect the “Proxy mode” checkbox under nginx settings. The feature is also available in Service Plans.
We would appreciate hearing your feedback on implementation of this functionality. Thanks in advance!
—AK
Anonymous
supported this idea
·
-
200 votesAnonymous
supported this idea
·
-
32 votesstarted · 6 comments · Feature Suggestions » Plesk (general) · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
63 votes
We’re already planning to implement this functionality in upcoming releases.
—ES
Anonymous
supported this idea
·
-
1,512 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 -
1,108 votes
An error occurred while saving the comment Anonymous
commented
+1 would love to have ClamAV in Plesk management.
-
18 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 Anonymous
commented
+1 need this!
-
98 votes
We are building an extension to help you use Composer straight from the Plesk interface. Help us make a better solution for you by taking a survey on how you use Composer.
The survey will take 4-6 minutes:
https://pt-research.typeform.com/to/LyPiPGBeta version of the Extension is available for Plesk Obsidian: https://docs.plesk.com/release-notes/obsidian/whats-new/
An error occurred while saving the comment Anonymous
commented
It is really important to us to have PHP Composer in Chroot Env :)
Anonymous
supported this idea
·
-
167 votes
Thank you for your input. We will explore the possibility of implementing YubiKey in upcoming releases.
Anonymous
shared this idea
·
-
395 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 Anonymous
commented
Also would love to have piwik integrated in plesk 12!
-
499 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 Anonymous
commented
Really important, good idea!
-
646 votes
An error occurred while saving the comment Anonymous
commented
Also really need this!
-
747 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
Need failover scenario in Plesk !!