filezilla sftp server does not prompt for certificate

I'm a bit confused, though, because in your documentation, certificates are really only mentioned under FTPS, but SFTP is only concerned with the server's public key. The only way I've managed to successfully connect is with a lot of exporting/converting to get the public key from the certificate (that the server is using), and into the correct format. I'm connecting to a test server with ServerValidation set to Automatic and by adding a public key file to known hosts as follows: ((SecureFTPConnection)ftpClient).KnownHosts.AddKnownHost(publishConfig.Host, publicKeyFile) In the worst-case scenario, this message. Download the most recent release of Secure FTP Server. This public key is derived from a certificate on the server, and needs to be in SSH (or SECSH) format. This message is to warn the client that the saved Host key does not match the incoming host key from the SFTP server. or update process does not reset or otherwise affect your server configuration or user settings.

If you still would like to implement FTPS (so the older, legacy protocol but now with TLS), you can get a Let's Encrypt certificate for the hostname of your server using one of the many ACME clients and install it into FileZilla.

You can read more about SFTP on numerous websites, such as SFTP protocol, clients, servers etc. Just to make sure I'm understanding this correctly: the main difference (when doing server validation) between FTPS and SFTP is that the client needs the server's certificate with FTPS but only the public key with SFTP. SFTP (SSH File Transfer Protocol) does not use TLS certificates and thus is not really the scope of this Community.

Filezilla sftp server does not prompt for certificate