FileZilla stuck at Initializing TLS
I am having an issue with FileZilla. I try to establish an FTP connection with my server but end up stuck at the same initial message after trying quite a few rounds. I am able to use the same host, username, password and port to login using Chrome browser but not for FileZilla. Any idea?
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 1 of 50 allowed.
Response: 220-Local time is now 16:13. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 15 minutes of inactivity.
Command: AUTH TLS
Response: 234 AUTH TLS OK.
Status: Initializing TLS...
So far I tried download and install the older version but different error appears (failed to retrieve directory listing) reference to https://trac.filezilla-project.org/ticket/9995
Had this problem also, just go to file ->site manager. On the encryption drop down change to "use only Plain FTP (insecure). And that's it!
I faced the same issue many times, and when the hosting provider and filezilla forums couldn't help, i myself tried digging it deeper to figure out the exact problem. Putting it altogether for you all..
There are mainly two scenarios under which you can face this issue..
First: Server you are trying to access doesn't support connection over TLS.
Second: You ISP doesn't allow to initialize TLS on FTP.
But since now most of the standard hosting providers do support FTP over TLS, so the issue is mainly due to ISP, Especially mobile operators disallow this sought of connection, so people using mobile hotspots are more likely to face this problem. Like in India half of the mobile operators doesn't allow FTP over TLS. Just switch the data SIM or the ISP and try again.
The most likely reason is that the server you're connecting to does not support FTP over TLS. Try connecting with another protocol, or with plain FTP instead and see what happens.
There is a LENGTHY bug report on the Filezilla bug tracker website from people re-opening a bug on this issue, because the feedback FileZilla gives is less than helpful in this situation.