COMMAND> AUTH TLS 234 AUTH TLS OK. ERROR> Connection attempt failed.


I am trying to connect to a site using FTP over TLS (explicit) with port 21.

I am able to connect with no problems using other FTP clients but I cannot with FTP Voyager.

I am able to connect using standard FTP.

I am also able to connect with SSH which I didnt know I could.

My password is correct.  Again, I can connect with many other clients using the same settings.

Could it have anything with FTP Voyager thinking the server certificate is insecure?

ANy setting to allow insecure certificates to try that?

ANy help is apprecoated.


This is the log:

STATUS> Resolving host ""...

STATUS> Connecting to "" on port 21.

STATUS> Connected to from

220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

220-You are user number 1 of 50 allowed.

220-Local time is now 10:32. Server port: 21.

220-This is a private system - No anonymous login

220-IPv6 connections are also welcome on this server.

220 You will be disconnected after 15 minutes of inactivity.



ERROR> Connection attempt failed.  Retrying in 3 seconds...

  • One of our ftp users is seeing the same problem.  Our FTP server (pure-ftpd) is configured to use FTP over TLS (Explicit).  Our server logs indicate that FTP Voyager continues to use cleartext after the AUTH TLS OK response from the server;

    May 21 15:56:23 ftpserver pure-ftpd: (?@10.x.x.x) [INFO] New connection from 10.x.x.x

    May 21 15:56:23 ftpserver pure-ftpd: (?@ [WARNING] Sorry, cleartext sessions are not accepted on this server.#012Please reconnect using SSL/TLS security mechanisms.

    Contrast this with other clients like Filezilla or WinSCP which switch to encrypted sessions once AUTH TLS OK is received.  Looks like a bug with FTP Voyager to me.