Archived Forum Post

Index of archived forum posts

Question:

TLS 1.2 causes failed connection

Jul 26 '16 at 15:52

Upgrading to newest versions and getting the following error. Works fine with 2.0 but would like to upgrade to 4.6 framework.

With authTLS Enabled: ChilkatLog: Connect_Ftp2: DllDate: Jun 13 2016 ChilkatVersion: 9.5.0.58 UnlockPrefix: PACSFDFTP Architecture: Little Endian; 32-bit Language: Visual C++ 12.0 (32-bit) VerboseLogging: 0 ProgressMonitoring: enabled: yes heartbeatMs: 0 sendBufferSize: 65536 --ProgressMonitoring ImplicitSsl: 0 AuthTls: 1 AuthSsl: 1 ftpConnect: Hostname: safetrans.wellsfargo.com Port: 21 IdleTimeoutMs: 60000 socketOptions: SO_SNDBUF: 262144 SO_RCVBUF: 4194304 TCP_NODELAY: 1 SO_KEEPALIVE: 0 --socketOptions readCommandResponse: replyLineQP: 220 Welcome to Axway Gateway FTP server --readCommandResponse initialStatus: 220 initialResponse: 220 Welcome to Axway Gateway FTP server converting to secure connection... authTls: simpleCommand: sendCommand: sendingCommand: AUTH TLS --sendCommand readCommandResponse: replyLineQP: 234 Security data exchange complete. --readCommandResponse --simpleCommand clientHandshake: clientHandshake2: getPrivateKey: certGetPrivateKeyAsDER: toPrivKeyDer: This is a public key, not a private key. --toPrivKeyDer --certGetPrivateKeyAsDER Unable to export the private key. --getPrivateKey sendCertificateVerify: CertificateVerify using TLS 1.2 with MS Crypto API is not supported. Use TLS 1.1 or lower. --sendCertificateVerify Failed to send client certificate verify message. --clientHandshake2 --clientHandshake Client handshake failed. (1) connectionClosed: 0 Failed to convert channel to SSL/TLS --authTls --ftpConnect Failed to connect to FTP server. Failed. --Connect_Ftp2 --ChilkatLog

With authTls Disabled ChilkatLog: Connect_Ftp2: DllDate: Jun 13 2016 ChilkatVersion: 9.5.0.58 UnlockPrefix: PACSFDFTP Architecture: Little Endian; 32-bit Language: Visual C++ 12.0 (32-bit) VerboseLogging: 0 ProgressMonitoring: enabled: yes heartbeatMs: 0 sendBufferSize: 65536 --ProgressMonitoring ImplicitSsl: 0 AuthTls: 0 AuthSsl: 1 ftpConnect: Hostname: safetrans.wellsfargo.com Port: 21 IdleTimeoutMs: 60000 socketOptions: SO_SNDBUF: 262144 SO_RCVBUF: 4194304 TCP_NODELAY: 1 SO_KEEPALIVE: 0 --socketOptions readCommandResponse: replyLineQP: 220 Welcome to Axway Gateway FTP server --readCommandResponse initialStatus: 220 initialResponse: 220 Welcome to Axway Gateway FTP server converting to secure connection... authTls: simpleCommand: sendCommand: sendingCommand: AUTH SSL --sendCommand readCommandResponse: replyLineQP: 234 Security data exchange complete. --readCommandResponse --simpleCommand clientHandshake: clientHandshake2: getPrivateKey: certGetPrivateKeyAsDER: toPrivKeyDer: This is a public key, not a private key. --toPrivKeyDer --certGetPrivateKeyAsDER Unable to export the private key. --getPrivateKey sendCertificateVerify: CertificateVerify using TLS 1.2 with MS Crypto API is not supported. Use TLS 1.1 or lower. --sendCertificateVerify Failed to send client certificate verify message. --clientHandshake2 --clientHandshake Client handshake failed. (1) connectionClosed: 0 Failed to convert channel to SSL/TLS --authTls --ftpConnect Failed to connect to FTP server. Failed. --Connect_Ftp2 --ChilkatLog