Allow FTPS to use certificates other than the one used to secure Plesk
Currently only the certificate used to secure plesk is used for all FTPS connections.
It would be useful to be able to use other certificates for FTPS connections, specifically ones already used for other domains.
Roland K. commented
This need to be done!
This needs to be implemented!
Great, great, great idea!
This is very important for my customer accounts! The domain needs the secured connection ... not the Plesk host.
This is very important for my customer accounts!
That must be implemented!
Felix Gade commented
I was confused that it was not implemented yet... it disturb the common smooth handling of Plesk!
Michaël Frippiat commented
Agree. This should be implemented!
I agree! I have a couple of domains and it does not make a good impression that there always is a warning about the different domain name - e.g. in FileZilla.
ali parsa commented
I am trying to get PCI/DSS compliance but I have stucked on this issue because of having multiple domains on my server and certificate not valid for target domain.
This is important for users of shared servers. FTPS should use the certificate that's assigned to the site, not a certificate that belongs to the server host.
Current solution is totally unusable. Everytime you connect to secured ftp of domain.com you get a warning that certificate common name does not match the domain you are connecting to. How it is supposed to work?
This feature must have been implemented years ago.