filezilla failed to retrieve directory listing on tls

The connection for the data socket is closed identically with TLS v1.2 or TLSv1.3. Considering all other clients I tried worked, and the entire dir listing is in the log, I don't believe there is any bug in multiple different server vendors code bases for TLSv1.3. But if I swap it back to TLSv1.3, the FZ fails. If the only change I make is setting TLSv1.2 as the TLS version for my ServerSocket, then FZ is fine. We didn't make a single code change in CrushFTP to support TLSv1.3.nor should we need to as the underlying JVM since Java 13+ has supported TLSv1.3 in a stable manner. I tried a dir listing, and the entire dir listing shows in the FZ log, but apparently it doesn't like how the socket is closed.? Session is never disconnected, and the entire dir listing is just didn't display it for unknown reasons.Įvery Java VM I have used CrushFTP Server on with TLS v1.3 works with all other TLSv1.3 clients *except* FileZilla. Only FileZilla client complains.and it looks to be a false complaint at that. For reference though, with absolutely no change at all, the following other clients *DO* work with TLS v1.3. I am a server vendor for example, and I cannot make FZ client work with our server. Re-openning this as your reply saying to contact the server vendor got my attention.

Filezilla failed to retrieve directory listing on tls