Marco Marsala
My feedback
-
87 votes
-
44 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.—
IG -
174 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
-
1 vote
-
4 votes
-
2 votes
-
961 votesopen discussion · 113 comments · Feature Suggestions » Plesk (general) · Flag idea as inappropriate… · Admin →
All needed system tools are already available, you just need to write a GUI to set them up:
- MySQL supports replication; actually it can be set up via Tools & Settings > Database Servers > phpMyAdmin > Replication;
- Dovecot supports master/master replication using dsync: https://wiki.dovecot.org/Replication
- File replication: mmmmhh
-
1 vote
And maybe allow release upgrade from control panel, as already done with package upgrades.
-
1 vote
-
1 vote
-
16 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.
—
ET -
1 vote
-
1 vote
-
8 votes
And maybe the abuse contact for the IP owner (via RIPE Database Query) and an extract of the log. Just things ready to send abuse reports.
-
13 votes
-
4 votes
-
3 votes
hank 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.
—
IG -
6 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.
__
IG -
1 vote
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
— rk
-
3 votes
The problem may be in that destination server will not be able to use specified version of PHP for the migrated domain because of absence in official OS vendor’s repository. To prevent this kind of problems we see improvement of pre-migration checker which will notify you about possible post-migration issues. After that, the server administrator must solve the problem himself. The automatic resolving of these incompatibilities looks very dangerous.
—
IGWhile migrating some subscriptions only, it is not useful and confusing that that Plesk Migrator complain about:
- missing plesk-mobile extension on destination server
- missing Courier-IMAP (if destination server uses Dovecot)> "in that destination server will not be able to use specified version of PHP for the migrated domain because of absence in official OS vendor’s repository"
Infact I installed the specified version via Plesk Installer.
> "The automatic resolving of these incompatibilities looks very dangerous."
No, if you limit to those PHP parameters you can already change via Plesk UI on a per-domain basis. Here is the list: https://snag.gy/VPKklM.jpg
Please check other glitches in my comments too.
Too, clicking "Details" link near to a failed migration freeze the browser for ages to open the popup even with short outputs.
Other small glitches I've found:
If a migration fails while performing database migration, business objects aren't fully migrated too and this isn't noticed at all. Even worse, when you fixed the database issue and retry the migration, clicking the button "Re-sync", a clever popup asks what objects has to be re-synced, but the checkbox "Business objects" is *deselected* by default. This is confusing and unexpected, as the database migration is not related to business objects.
Use case:
1) Migrate testdomain.tld from target server A to destination server B;
2) Migration fails because MySQL is older on the destination server and some features aren't supported;
3) You fix the database issue and retry the database migration only, because files and mails we're migrated without issues.
4) The resulting domain is missing Let's Encrypt certificates.
5) Re-syncing migration selecting checkbox "Business objects" restores the missing certificate.
The SSL certificate is not applied to webserver listening on port 8443, even if installed for the domain.
Live example:
https://www.holidayworld.it/ shown as secure
while https://www.holidayworld.it:8443/ is shown as not secure