Connecting over TLS

[jiska]

I've performed a test from ftptest.net for TLS Expicit and everything works fine, however when I try to connect with Filezilla Client it times out with the logs below. If I turn TLS off, it connects and works fine.

Any ideas?

FTPTEST.NET:
Results

Your server is working and assorted routers/firewalls have been correctly configured for explicit FTP over TLS as performed by this test. However there have been warnings about compatibility issues, not all users will be able to use your server.

For maximum compatibility, consider resolving these warnings.


Client side:
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Error: Disconnected from server: ECONNABORTED - Connection aborted
Error: Failed to retrieve directory listing

Server side:
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> Connected on port 21, sending welcome message...
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220-FileZilla Server 0.9.60 beta
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220 Welcome to Auto-IT
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> USER xxxx
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> 331 Password required for xxxx
(001225)26/02/2019 11:17:28 AM - (not logged in) (xxx.xxx.xxx.xxx)> PASS ***********
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> 230 Logged on
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> PWD
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> 257 "/" is current directory.
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> TYPE I
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> 200 Type set to I
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> PASV
(001225)26/02/2019 11:17:28 AM - xxxx (xxx.xxx.xxx.xxx)> 227 Entering Passive Mode (xxx.xxx.xxx.xxx,238,235)

[botg]

The log shows the client _not_ using FTP over TLS. Make sure to enable FTP over TLS in the client.

[jiska]

Apologies - I must have posted the wrong log.

I found the problem in the end. I'd already connected to the server from the client before generating a certificate, so whilst the server cert had changed, the client was expecting a different certificate.

All good now.