• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Change FTPS certificate

parsa25eng

New Pleskian
Hi.
I have Plesk 17.0.17 on my Linux Centos 7.5 server and I have configured some domains on it.
For one of this domains I am trying to use FTPS. But FTPS uses Plesk panel certificate and cause security error on FTP clients.
Is is possible to provides domain's own certificate for FTPS? or is it possible to configure custom certificate for FTPS?
thanks.
 
Hi.
I have Plesk 17.0.17 on my Linux Centos 7.5 server and I have configured some domains on it.
For one of this domains I am trying to use FTPS. But FTPS uses Plesk panel certificate and cause security error on FTP clients.
Is is possible to provides domain's own certificate for FTPS? or is it possible to configure custom certificate for FTPS?
thanks.
If you are just wanting to use a different certificate than the one protecting Plesk panel, and don't mind that it covers all ftp connections to every domain, you can put code in a custom ProFTPd configuration file found here:
/etc/proftpd.d/my-custom-proftpd-settings.conf
Code:
<Global>
   <IfModule mod_tls.c>
       # use a self-signed or other cert for FTPS/SFTP while using letsencrypt to secure plesk
       TLSRSACertificateFile /etc/path/to/custom/certificate.pem
       TLSRSACertificateKeyFile /etc/path/to/custom/certificate.pem
   </IfModule>
</Global>
Remember to restart the service after placing this code: service xinetd restart

I created a self-signed cert for mine so Let's Encrypt could still cover the Plesk Panel, and my FTP cert for all my customers only has to be accepted once per domain, as it expires in 2047. ;-)
 
Back
Top