+1

I think this is a critical feature nowadays.

We also need this feature! Some of the web apps we are developing cannot get past the "there is an issue with the server certificate" warning.

5 years now.... hopefully we will get this anytime. This should really be a basic feature!

This must be a joke PLESK. The question was asked June 09, 2017 and 5 years later nothing has happened. Pull up your pants Plesk.

+1 for SSL for ftp.clientdomain.ltd

@erdea solutions I absolutely agree! For a short solution, it would be helpful to allow custom domain names for creating plesk certificate, so you can add ftp.customerdomain.com as certificate alias for using customers domain name for ftp connections.

It's a feature that normally should not be voted to implement it. For professional use of plesk, it's a shame to tell the clients, that they can't use ftp.domain.tld, but use the domain of the plesk server... Please, implement it.

The absolute mess that is SSL certificates in Plesk and Windows is not made any less by the fact that certificates for FTP must be applied manually, directly in IIS Manager – nor by the fact that there is absolutely NO WAY to identify the correct certificate between Plesk and IIS Manager, since the ONLY thing each shows about a certificate is stuff the other does not show.

This takes several days of hair-pulling and frustration every single time a Lets Encrypt certificate expires, until somehow the magic bullet is found that lets users actually connect without hostname mismatches, missing certificates and other obstacles.

Utterly, utterly hopeless.

Filezilla no longer alows override of the default SSL (Mine in plesk says the default cert is now an empty one) and my ftp does not support TLS - let's encrypt does not show in the list of certs when selecting the drop down from tools - Does this mean every 3 months I need to somehow generate a cert into the server pool or re-create a new default or what - Secure FTP is now a MUST for a lot of financial certifications

+1

Hello @webdiz,

Plesk has SSL wildcard certificate support since long time already via Let's Encrypt.
It can also be used as white-label solution for the mail server same as a branded login URL to the admin panel.

Only FTPS connections are still using the single main SSL certificate of the host server.

Kind regards,
Michael

Would be very important to allow alternative domain names or event better, wildcard certificate generation with Let's Encrypt.

For example:

plesk.example.com (Plesk panel)
ftp.example.com (FTP)
mail.example.com (Mail server)

And this with the same certificate.

Long overdue! Should be a basic nowadays

All resellers would love that feature to have a white-label solution also for FTPs connections.

This should be implemented years ago.... everyone wants to use secure ftp nowadays.

After trying various things, I've found winScp works well.

Please implement this feature.

Plss *** son as posible more than 3 years!

I agree with this request.

It makes sense to use the domain certificate rather than the host one which gives the customer a certificate error and wastes ones time having to explain why.

Please implement this feature.