Connection issue after update to 3.10.0.1? Nothing wrong with your host... solution..

[inistea]

By the attitude I am reading, the support for the latest version is "largely being ignored" too.
Version 3.9.0.6 was working perfectly for me.
Best idea is not to fix what 'aint broke.

Thank you, Alan Beasy, for this and that !

[botg]

Version 3.9.0.6 was working perfectly for me.

As does 3.10.0.2, both work perfectly for you and everybody else.

The problem is with your server, it's the server that isn't working properly.

[tcat]

3.10.0.2 not working for me. I have auto updated for 10 years and never had a problem logging in.

Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Server does not support non-ASCII characters.
Status: Connected
Status: Retrieving directory listing of "Y:\"...
Command: CWD Y:\
Response: 553 Prohibited file name: Y:\
Command: PWD
Response: 257 "/" is your current location
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PASV
Response: 227 Entering Passive Mode (198,252,99,95,54,4)
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing

[Jefferson]

Have been auto-connecting for years to the server using Filezilla then
both myself and my colleague just updated to 3.10.0.2, how we both can't login to our servers.
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Error: GnuTLS error -110: The TLS connection was non-properly terminated.[/color]
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
------------------------------------------------------------
However if we choose:
"Encryption - Only use plain FTP (insecure)"
we can then login to the server... something is broken within the TLS.

[persalmi]

Version 3.9.0.6 was working perfectly for me.

As does 3.10.0.2, both work perfectly for you and everybody else.

The problem is with your server, it's the server that isn't working properly.

I have this issue connecting to one of my customers ISP hosted FTP servers. The problem with it is that it works perfectly well with 3.10.0.2 if I connect from my home office but not from the Corporate network where I normally do my work. The Corporate network is slightly more limited but allowed the previous versions of Filezilla to connect. I do not have the Power to demand Changes to the Corporate network without pretty good arguments and proof of exactly what is wrong.

All previous versions of Filezilla worked well from both types of networks. So the problem is not explained by "it is the servers fault". Nothing has changed in the Corporate network or on the server side, only the Filezilla client was updated. Is there an official way to download the older version that doesn't enforce this new "broken" way of connecting to the server?

Or... what kind of Changes would the firewall/Proxy/security administrators at work have to do to make it work?

/Per

[boco]

3.10.0.2 not working for me. I have auto updated for 10 years and never had a problem logging in.

Because you never used FTP over TLS (Explicit) before. Workaround: Set Encryption to Plain in the Site Manager. Proper fix: Have the server fixed.

Have been auto-connecting for years to the server using Filezilla then
both myself and my colleague just updated to 3.10.0.2, how we both can't login to our servers.
[...]
However if we choose:
"Encryption - Only use plain FTP (insecure)"
we can then login to the server... something is broken within the TLS.

TLS support in your server (or in a firewall along the way) is broken.

Or... what kind of Changes would the firewall/Proxy/security administrators at work have to do to make it work?

Your corporate firewall most likely blocks encrypted traffic. Set the Encryption to Plain in Site Manager, since I see no way to convince any corporate admin of the need to have non-supervised and non-controlled traffic leaving the corporate net.

[alanbeasy]

Version 3.9.0.6 was working perfectly for me.

As does 3.10.0.2, both work perfectly for you and everybody else.

The problem is with your server, it's the server that isn't working properly.

Absolutely DISGUSTING Site Admin!!!!!
This is the last time I will be dealing with FileZilla.
If 3.9.0.6 ever fails me I will use a different FTP.

[botg]

Absolutely DISGUSTING Site Admin!!!!!
This is the last time I will be dealing with FileZilla.
If 3.9.0.6 ever fails me I will use a different FTP.

First denial, now anger. Next up: Bargaining http://en.wikipedia.org/wiki/K%C3%BCble ... del#Stages



The fact remains that your server or a firewall in front of it isn't configured correctly for FTP over TLS. This problem can only be resolved by fixing the server.

[lolguy43uk]

I've just rolled back to 3.9.0.6 and it has cured the problem.

[boco]

No, it has not.

[botg]

Using an older version is the same as forcing plaintext FTP with your server in the new version. If you were to use FTP over TLS in the old version if would fail as well.

This is a server-side issue that can only be fixed by your server administrator or server hosting provider.