• 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!
  • 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.

Own SSL certificate is marked as unknown while connecting via FTPS

sparkxp

Basic Pleskian
Hi,

I'm bought a domain based SSL certificate (hosting.mydomain.com) for my Plesk panel. This is working fine.
Now I decided to use it for FTPS too. So I took a look in the /etc/proftpd.conf and saw that mod_tls is already implemented. The TLSRSACertificateFile points to /opt/psa/admin/conf/httpsd.pem, which is my working panel certificate.
But if I try to connect via FTPS to the FTP, I'm getting a message that the certificate is unknown. Within the message I can see that the correct certificate is used.
But why does it say its unknown??

I'm using WinSCP with the following login credentials.

Host: hosting.mydomain.com
Protocol: FTP
Port: 21
Encryption: tryed SSL and TLS explicit

My /etc/proftpd.conf

<IfModule mod_tls.c>
TLSEngine on
TLSRequired off
TLSLog /opt/psa/var/log/ftp_tls.log
TLSRSACertificateFile /opt/psa/admin/conf/httpsd.pem
TLSRSACertificateKeyFile /opt/psa/admin/conf/httpsd.pem
TLSVerifyClient off
TLSRenegotiate none
TLSOptions NoSessionReuseRequired
</IfModule>

WinSCP message:
proftpd.jpg
 
Back
Top