Anonymous
My feedback
-
90 votes
Hi everyone,
This seems to be important, so we’ll address it in one of the upcoming Plesk releases.
Please continue to vote so we can accurately assess the popularity of this request.
— AK
An error occurred while saving the comment Anonymous
supported this idea
·
-
49 votesAnonymous
supported this idea
·
-
40 votesAnonymous
supported this idea
·
-
114 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.—
IGAnonymous
supported this idea
·
-
179 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.
—
ETAnonymous
supported this idea
·
-
244 votes
We have an article with an instruction how to set up django on Plesk server https://www.plesk.com/blog/product-technology/plesk-and-django
So, now we would like to get a feedback what is the most critical things you need to manage with Plesk regarding django.Anonymous
supported this idea
·
-
264 votes
As UserVoice staff cleaned up the most of twisted voices, I’ve returning this suggestion to open discussion.
Everyone, please continue voting for this feature if you consider it important.
—IB
Anonymous
supported this idea
·
-
148 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
Since Plesk Onyx panel admin will be able to install different MySQL versions as a Docker containers, then the DB servers can be connected as remote DB to Plesk.
SE
Anonymous
supported this idea
·
-
202 votesAnonymous
supported this idea
·
-
548 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
·
-
397 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.
—
IGAnonymous
supported this idea
·
-
502 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
·
-
1,529 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.
—
AAAnonymous
supported this idea
·
-
1,114 votesAnonymous
supported this idea
·
I also ask myself what changes I've made before I resync a subscription. That information would be very helpful !