gnuTLS Error -110 The TLS connection was non-properly terminated.

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
wds_chr
500 Command not understood
Posts: 3
Joined: 2022-11-23 10:20
First name: Chris
Last name: Woods

gnuTLS Error -110 The TLS connection was non-properly terminated.

#1 Post by wds_chr » 2022-11-23 10:29

We have a FTP Server running Filezilla Server 1.5.1. Recently i've noticed a error logs on the server:

<Date> Info [Type] Message
<23/11/2022 10:13:03> FTP Session 8484 XXX.XXX.XXX.XXX User [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<23/11/2022 10:13:03> FTP Session 8484 XXX.XXX.XXX.XXX User [Status] Client did not properly shut down TLS connection
<23/11/2022 10:13:03> FTP Session 8484 XXX.XXX.XXX.XXX User [Error] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.

Is this something on the users side? or something i can fix on the server side?

Users are starting to reprot that they cannot connect to the server because of this error. I've tried everything and i'm honestly stumped on this.

Any help would be really appreciated!

User avatar
botg
Site Admin
Posts: 34582
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: gnuTLS Error -110 The TLS connection was non-properly terminated.

#2 Post by botg » 2022-11-23 12:02

Context matters. What are the preceding log lines for this FTP session?

wds_chr
500 Command not understood
Posts: 3
Joined: 2022-11-23 10:20
First name: Chris
Last name: Woods

Re: gnuTLS Error -110 The TLS connection was non-properly terminated.

#3 Post by wds_chr » 2022-11-23 13:55

The only other logs surrounding these -100 errors are relating to other sessions. In this case, session 8484 was ended.

I've attached log export from yesterday and today. We're getting quite a few guntls -110 errors. Just wondering if it's something we can fix as customers are reporting that they get this error and then cannot connect to the server
Attachments
fz-logexport.txt
(1.01 MiB) Downloaded 2 times

User avatar
botg
Site Admin
Posts: 34582
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: gnuTLS Error -110 The TLS connection was non-properly terminated.

#4 Post by botg » 2022-11-24 09:41

<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Command] PASV
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Error] Leaser's get_port() returned 0.
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Error] No more tries left, giving up.
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Response] 425 Cannot prepare for data connection.
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Command] PORT 192,168,99,117,202,238
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Response] 200 PORT command successful.
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Command] RETR SP20220801_001.xlsx
<23/11/2022 10:13:03> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Response] 150 Starting data transfer.
<23/11/2022 10:13:23> FTP Session 8485 148.252.42.161 PCSup_Spectrum [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Your passive mode port range is far too narrow. Rule of thumb: Number of ports >= number of transfers that can be possibly be mad.

In addition, the client is behind a NAT router. However the client hasn't been made aware of this and is using a private IP address in the PORT command. Most likely the client's NAT router doesn't have the corresponding ports forwarded either.

wds_chr
500 Command not understood
Posts: 3
Joined: 2022-11-23 10:20
First name: Chris
Last name: Woods

Re: gnuTLS Error -110 The TLS connection was non-properly terminated.

#5 Post by wds_chr » 2022-11-24 11:51

So is this something we can solve or is it down to the individual customers that connect to our server?

I've changed the passive mode ports to 49512-65534 on the server, as it only has port 990 listed.

how would we tell the server client that it's behind a NAT router? I can't see any option in the Network wizard or the actual configuration itself?

User avatar
botg
Site Admin
Posts: 34582
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: gnuTLS Error -110 The TLS connection was non-properly terminated.

#6 Post by botg » 2022-11-24 13:17

The user of the client software need to configure the client. Best to tell them via telephone, in person or via carrier pigeon.

Post Reply