Use Lets Encrypt to secure FTPs connections
Hi,
I usually use the ftp.site.com subdomain for the client FTP connections.
And to secure those connections I enabled FTPs. But at this point the users receive a certificate host name mismatch because the FTPs connection is being setup using the VPS Lets Encrypt cert.
It would be nice to use the Lets Encrypt certificate service also to secure the FTPs connections.
Thanks!
Stephan
shared this idea
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
-
Greg
commented
This needs to be implemented!
-
Anonymous
commented
Great, great, great idea!
-
Anonymous
commented
Too much money to still not having it :(
-
Anonymous
commented
This is very important for my customer accounts! The domain needs the secured connection ... not the Plesk host.
-
Anonymous
commented
This is very important for my customer accounts!
-
Anonymous
commented
Definitely what we need! Thank you Plesk and Lets Encrypt team!
-
Gil
commented
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!
-
sysadmin
commented
Hello,
I'd like to add my request for priority on this, especially since it is a known issue which, per support ticket response, is close to being worked on:
>> The feature of having per-domain SSL certificates
>> for FTP by Let's Encrypt is already known for our developmentThis would be a big help. Currently we have to manually renew the certificates covering the FTP service, setting reminders for staff to check every server periodically. (In other words, it is possible, but is currently a manual process, when everything else about Let's Encrypt in Plesk is slick and automated). Thank you.
-
Phantasia
commented
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.
-
Harry
commented
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.
-
rdk
commented
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.
-
Roman
commented
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.
-
Anonymous
commented
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.
Thank you
-
Hello.
JFYI: in case of Plesk Onyx 17.5+ and Let's Encrypt 2.3+:
FTP server is secured with the Panel certificate.
Mail server also can be secured with the Panel certificate.
The Panel certificate can be issued with help of the extension. -
DaveMurray
commented
Currently only web admin url, webmail and web server supported by the extension. We must complete support including mail server certs, ftp certs, or any service provided by plesk serving anything...