Anonymous
My feedback
23 results found
-
16 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
217 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.
— AY
An error occurred while saving the comment Anonymous
commented
Plus addressing/sub addressing are now standard and required if we are migrating customers into Plesk or Plesk Premium Email. This needs to be addressed in about 30 minutes..
Anonymous
supported this idea
·
-
172 votes
Thank you for your input! We are planning to implement this functionality in upcoming releases. The request is registered as: PPM-2517
Everyone, please continue voting for this feature if you consider it important.
— ES
Anonymous
supported this idea
·
-
297 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
Anonymous
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
Anonymous
supported this idea
·
-
229 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
·
-
435 votesAnonymous
supported this idea
·
-
490 votesAnonymous
supported this idea
·
-
709 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
Anonymous
supported this idea
·
-
47 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
Anonymous
supported this idea
·
-
136 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
·
-
90 votesAnonymous
supported this idea
·
-
281 votes
Please note, Plesk has supported the version of Mailman provided by OS vendor by default.
The Mailman 3 is shipped by default on Ubuntu 18 and Debian 10.
Please keep voting if this request is still actual for you.
—
AAAnonymous
supported this idea
·
-
54 votes
Good news! Despite the low number of votes that this request got, from some additional reports Plesk understands that this is a critical function for some users. We do not have an ETA yet, but it will be worked on in the scope of upcoming feature enhancements.
Anonymous
supported this idea
·
-
174 votes
Everyone, please continue voting for this feature if you consider it important.
— rk
Anonymous
supported this idea
·
-
52 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
·
-
380 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.
— AY
Anonymous
supported this idea
·
-
1,051 votes
Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.
Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:
#1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)
#2. Backup to different storages (like daily to FTP and monthly to Google Drive)
#3. Multiple Storages of the same type (like 2 different FTP servers)
ID in our Issue Tracker: PPM-1701
-DLAnonymous
supported this idea
·
-
1,573 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
·
-
526 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
·
.png){kind=link}
I have already opened a ticket for this, please, this is critical as we plan to migrate all our SmarterMail clients into Plesk Premium Email.