I suggest you ...

← Feature Suggestions

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!

248 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Stephan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

50 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Alan Sheppard commented  ·   ·  Flag as inappropriate

    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

  • Michael commented  ·   ·  Flag as inappropriate

    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

  • vaelu commented  ·   ·  Flag as inappropriate

    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.

  • Michael commented  ·   ·  Flag as inappropriate

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

  • Roland K. commented  ·   ·  Flag as inappropriate

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

  • Terry commented  ·   ·  Flag as inappropriate

    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.

  • Kirk commented  ·   ·  Flag as inappropriate

    This limitation is really counter-productive. It basically voids FTPS for domains since any FTP client will reject the panel certificate and throw an error. The user has to either accept the wrong cert or it scares them off and they can't use a secure form of FTP. Ridiculous.

← Previous 1 3

Feature Suggestions: Security

Categories

Feedback and Knowledge Base

(thinking…)