boco wrote:Why change the default behaviour rather than offer it as an upgrade for servers which support it.
I think you don't get it:
The new default is "Use explicit FTP over TLS
if available". That means, if the server announces support for FTP over TLS FileZilla attempts to use it. Nothing wrong with that. What IS actually wrong are thousands of hosting and ISP server that pretend to support FTPS but then bail out. That's not the way to configure a server right, either support it correctly or deny it outright.
My ISP have tested the TLS connection and report that it is actually working.
I am still unable to use it no matter what settings I use.
From the log file below, it appears to make the connection and then reports that it cannot make the connection because it refuses to talk to the router.
How is it making a connection to the server if it cannot get past the router?
----- log ------------------
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
Status: Disconnected from server
Status: Connecting to xx,xxx,xxx,xxx:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Server does not support non-ASCII characters.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is your current location
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PORT xxx,xxx,x,xxx,xxx
Response: 500 I won't open a connection to (xxx router IP xxx) (only to xx,xx,xxx,xxx)
Command: PASV
Response: 227 Entering Passive Mode (xx,xxx,xxx,xxx,xx,xx)
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing
-------------------------------------------------------------------------------------------------
I am not really bothered why it doesn't work or who's fault it is, I am just frustrated that I am wasting my time trying to sort out a problem which has been introduced by a software update.