FileZilla Forums

Hello,
I was uploading to my server using FIlezilla client when the internet connection disconnected unexpectedly.
I re-connected and logged in to filezilla again to continue the upload but I got the following error when opening the files on the server to which I wanted to upload:

GnuTLS error -110: The TLS connection was non-properly terminated.

How do I resolve this error message please?
Thanks,
Barry

Complete logs, please. The mentioned error often is a red herring, the real problem comes before that.

One possible cause could be that the files on the server are still open/locked, due to the sudden interruption. Even if your side of the connection broke, the other side on the server could be still open until an eventual timeout happens.

Complete logs as follows when I try to connect to the server:

Status: Resolving address of waws-prod-db3-011.ftp.azurewebsites.windows.net
Status: Connecting to 40.85.77.3:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (40,85,77,3,39,158).
Command: LIST
Response: 150 Opening BINARY mode data connection.
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: The data connection could not be established: ECONNABORTED - Connection aborted
Response: 550 The network connection was aborted by the local system.
Error: Failed to retrieve directory listing
Status: Disconnected from server: ECONNABORTED - Connection aborte

If I am waiting for an eventual timeout on the server side, how long would that take?

Thank you for your assistance.

Response: 550 The network connection was aborted by the local system.

That message comes from the sever, the local system in this case is the server's system.

Check the server system logs for more information why the server system decided to abort the connection.

For information, this issue appears to have resolved itself (passage of time). I guess it was a matter of waiting for the issue on the server to timeout.
Regardless, thanks for your input.
Barry