Initializing TLS / GnuTLS error -110

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
Dreamking
500 Command not understood
Posts: 2
Joined: 2018-10-18 15:25
First name: Joseph
Last name: Goncalves

Initializing TLS / GnuTLS error -110

#1 Post by Dreamking » 2018-10-18 15:42

Hello Everyone,

I am currently working with someone who was recently provisioned to work with our FileZilla FTPS site. When they try to connect to the server using the information given to them they get stuck at Initializing TLS which times out after 20 seconds and tries again only to experience the same error and then close the connection. Log is below.

Status: Resolving address of *****************
Status: Connecting to ***************************
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server

I confirmed with multiple people across different networks that they can access the server with the users account. I also reached out to the users I.T. team and they confirmed that nothing in the firewall should be blocking the connection. We also made sure that the users Firewall was disabled and it was. I watched a video that found a resolution by increasing the timeout time. I asked the user to set their timeout to 90 seconds but now we're seeing the GnuTLS Error -110. Log is below.

Status: Resolving address of **********************
Status: Connecting to *****************
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ************
Status: Connecting to *************
Status: Connection established, waiting for welcome message...
Response: 220-FileZilla Server 0.9.57 beta
Response: 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
Response: 220 Please visit https://filezilla-project.org/
Command: AUTH TLS
Response: 234 Using authentication type TLS
Status: Initializing TLS...
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server

Some information that may help, the user is currently using version 3.37.4 of FileZilla Client.
We require FTP over TLS with plain FTP disallowed. We also allow Explicit and Implicit FTP over TLS which use the same port as the Normal FTP connection.
Also when we asked the user to connect to the server through the browser they got a login prompt. Granted the credentials didn't work but at least they were able to get some level of server connection.

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

Re: Initializing TLS / GnuTLS error -110

#2 Post by botg » 2018-10-18 18:16

Sorry, we cannot support outdated versions of FileZilla Server.

User avatar
boco
Contributor
Posts: 26940
Joined: 2006-05-01 03:28
Location: Germany

Re: Initializing TLS / GnuTLS error -110

#3 Post by boco » 2018-10-18 18:17

First, please update your FileZilla FTP Server to the latest version, outdated versions receive no support.

Second, using the same port for Plain/Explicit FTP over TLS and Implicit FTP over TLS does NOT work. Implicit FTPS definitely requires a separate port (990 by default).
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org

Dreamking
500 Command not understood
Posts: 2
Joined: 2018-10-18 15:25
First name: Joseph
Last name: Goncalves

Re: Initializing TLS / GnuTLS error -110

#4 Post by Dreamking » 2018-10-18 19:34

Oops, botg you're correct. We're using 990 as the port. We left it as default.

Post Reply