FileZilla Forums

Posted: **2021-12-22 02:13**

Hi All,

I have FileZilla Server 0.9.60 beta.
In FileZilla server I can see that users are able to connect.
However, there is one user who can't and get this error:

Code: Select all

Status:	Connecting to WWW.XXX.YYY.ZZZ:21...
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
Status:	Waiting to retry...
Status:	Connecting to WWW.XXX.YYY.ZZZ:21...
Status:	Connection established, waiting for welcome message...
Response:	220-FileZilla Server 0.9.60 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:	Connection timed out after 20 seconds of inactivity
Error:	Could not connect to server

It worked fine last time for the affected user a week and stopped all of a sudden.

On the FileZilla server I can see:

Code: Select all

(000238)22/12/2021 13:08:44 PM - (not logged in) (14.201.39.106)> Connected on port 21, sending welcome message...
(000238)22/12/2021 13:08:44 PM - (not logged in) (14.201.39.106)> 220-FileZilla Server 0.9.60 beta
(000238)22/12/2021 13:08:44 PM - (not logged in) (14.201.39.106)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000238)22/12/2021 13:08:44 PM - (not logged in) (14.201.39.106)> 220 Please visit https://filezilla-project.org/
(000238)22/12/2021 13:08:45 PM - (not logged in) (14.201.39.106)> AUTH TLS
(000238)22/12/2021 13:08:45 PM - (not logged in) (14.201.39.106)> 234 Using authentication type TLS
(000238)22/12/2021 13:09:05 PM - (not logged in) (14.201.39.106)> disconnected.
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> Connected on port 21, sending welcome message...
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> 220-FileZilla Server 0.9.60 beta
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> 220 Please visit https://filezilla-project.org/
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> AUTH TLS
(000239)22/12/2021 13:09:10 PM - (not logged in) (14.201.39.106)> 234 Using authentication type TLS
(000239)22/12/2021 13:09:30 PM - (not logged in) (14.201.39.106)> disconnected.

Could you please advise hat it could be related to.

Posted: **2021-12-22 08:57**

Most likely a firewall is interrupting the connection. If it only affects one user, it stands to reason that this firewall probably sits close to the client.

Posted: **2021-12-22 21:27**

Firewall is off.
I can't even connect from FTP app on mobile phone.
I forgot to mention that I can connect over port 990.
21 port doesn't allow to connect though.

Posted: **2021-12-22 22:45**

Mobile providers hate FTP. Most block port 21 and/or FTP traffic (and even FTP over TLS Explicit sessions start out as unencrypted ones and can be identified as being FTP). Port 990 is often forgotten, it seems.

Posted: **2022-01-11 04:03**

Issue was resolved.
It was related to restriction on local firewall.

FileZilla Forums

Connection timed out after 20 seconds of inactivity

Connection timed out after 20 seconds of inactivity

Re: Connection timed out after 20 seconds of inactivity

Re: Connection timed out after 20 seconds of inactivity

Re: Connection timed out after 20 seconds of inactivity

Re: Connection timed out after 20 seconds of inactivity