in reply to SSL connect attempt failed

As a wild guess, I will speculate that you are declaring a certificate hash as SSL_key_file on line 22. If so, and the server's certificate has changed, you will need to update that choice of pinned certificate — after confirming with your provider that the certificate actually has changed instead of you observing a MITM attack.

Also, as another monk mentioned, you seem to be using very old modules — your provider may have discontinued support for SSL and TLS prior to 1.2; if your copies of the relevant libraries are too old to support TLS 1.2, you would not be able to connect.

Replies are listed 'Best First'.
Re^2: SSL connect attempt failed
by Anonymous Monk on Aug 13, 2020 at 13:17 UTC
    Is it possible to run Net::FTPSSL from the command line? I notice this line in the logs "not using SNI because hostname is unknown".

      On line 30, you blanked out an IP address. Because you are connecting to the server using an IP address, Server Name Indication (where the hostname is sent in cleartext as part of the initial TLS negotiation to allow a server handling multiple sites to choose which certificate to present) is not usable. If FileZilla connects successfully given the same IP address, SNI (or lack thereof) is not causing your problem.