FileZilla Forums

botg wrote:FileZilla now automatically uses FTP over TLS if the server accepts it. Unfortunately there are a few badly configured servers out there. These servers need to be fixed.

All cool with us but what is the FIX in question pls
Old proverb say's "Why fix it when it's not broken"

It's mostly expired certificates as well as incorrect firewall and NAT router configuration on the server that needs fixing.

botg wrote:FileZilla now automatically uses FTP over TLS if the server accepts it. Unfortunately there are a few badly configured servers out there. These servers need to be fixed.

In my case - i.e. Bluehost.com - it was a situation that I could fix. I did the following:
1. Logged into Bluehost and went to the Control Panel
2. Under Security, Click on "SSH/Shell Access"
3. Click on "Manage SSH Access". You may need to verify your identity with Bluehost at this point.
4. From the drop down, select "SSH Access Enabled" and click "Submit"

Now in FileZilla, create a new Account
1. Host is the FTP Address - e.g. ftp.somewhere.com
2. Protocol is "SFTP-SSH File Transfer Protocol"
3. User ID is your Bluehost User Id
4. Password is your Bluehost Password
5. Click "Connect" to establish a connection with Directory Listing!

This resolve the issue with 3.10 for me. And I'm glad to have the Secure Access for all of my future file transfers. It should prevent security issues in the future.

I'm getting the similar behavior since updating:

Status: Resolving address of mbdigit.com
Status: Connecting to 174.127.104.174:21...
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...
Status: Directory listing of "/" successful
Status: Retrieving directory listing of "/Theming"...
Command: CWD /Theming
Response: 250 OK. Current directory is /Theming
Command: PWD
Response: 257 "/Theming" is your current location
Command: PASV
Response: 227 Entering Passive Mode (174,127,104,174,200,255)
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing

However, if I change encryption back to plain FTP, filezilla 3.10.0 works perfectly.

I have been on my hosting tech support all morning and they also use filezilla and they said thay have tried it on to PCs and it is working correctly. What could be the problem with my configuration?

what ports on the firewall should be open for this?

@crash893

sftp: 22
implicit tls: 990

I followed BE55Roberts' advice, and it worked. When I contacted Bluehost to verify, Bluehost first suggested I select "Plain FTP" instead of "FTP over TLS", when I informed support of BE55Roberts' solution, he told me to do that.

Admins - is this an appropriate way to fix this?

BE55Roberts wrote:

botg wrote:FileZilla now automatically uses FTP over TLS if the server accepts it. Unfortunately there are a few badly configured servers out there. These servers need to be fixed.

In my case - i.e. Bluehost.com - it was a situation that I could fix. I did the following:
1. Logged into Bluehost and went to the Control Panel
2. Under Security, Click on "SSH/Shell Access"
3. Click on "Manage SSH Access". You may need to verify your identity with Bluehost at this point.
4. From the drop down, select "SSH Access Enabled" and click "Submit"

Now in FileZilla, create a new Account
1. Host is the FTP Address - e.g. ftp.somewhere.com
2. Protocol is "SFTP-SSH File Transfer Protocol"
3. User ID is your Bluehost User Id
4. Password is your Bluehost Password
5. Click "Connect" to establish a connection with Directory Listing!

This resolve the issue with 3.10 for me. And I'm glad to have the Secure Access for all of my future file transfers. It should prevent security issues in the future.

I have the same/similar issue with 3.10.0. FileZilla has always worked perfectly, and worked perfectly 5 minutes before I updated to 3.10.0. After that it didn't connect due to unrecognized certificate, and when I told it to accept the certificate it connected and then couldn't download the directory.

I've read other posts and answers. I don't have time to persuade hosting services to update their servers so my updated FileZilla will work, and neither do others. I've already reverted to the previous version, which still works perfectly and I simply won't update. Down the road there are other FTP clients that work too. I just wanted someone to know.

Hi everybody,
I joined up when I read 'nodirectorylisting' wishing to backdate Filezilla. That's exactly what I have done. Fortunately, I always keep old versions in my downloads folder, and was able to reinstall 3.9
No matter what I did (ports, firewalls, encryption etc) it simply would not connect. I have now set the program to never check for updates.

PTCO wrote:I followed BE55Roberts' advice, and it worked. When I contacted Bluehost to verify, Bluehost first suggested I select "Plain FTP" instead of "FTP over TLS", when I informed support of BE55Roberts' solution, he told me to do that.

Admins - is this an appropriate way to fix this?

No, it is only a workaround. The appropriate way to fix this is for the server administrators to fix their server.

igdent wrote:Hi everybody,
I joined up when I read 'nodirectorylisting' wishing to backdate Filezilla. That's exactly what I have done. Fortunately, I always keep old versions in my downloads folder, and was able to reinstall 3.9
No matter what I did (ports, firewalls, encryption etc) it simply would not connect. I have now set the program to never check for updates.

If everyone were to use that approach, we'd still be living in caves. Move forward, convince your server administrator or server hosting provider to fix their server.

since today with update
same problem another error:

Status: Nächsten Versuch abwarten...
Status: Auflösen der IP-Adresse für ++++++
Status: Verbinde mit +++++
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Antwort: 220 ProFTPD 1.3.5 Server (ProFTPD) [*********]
Befehl: AUTH TLS
Antwort: 234 AUTH TLS successful
Status: Initialisiere TLS...
Fehler: GnuTLS error -12: A TLS fatal alert has been received.
Fehler: Herstellen der Verbindung zum Server fehlgeschlagen

This version should, as a minimum, come with a warning to warn users that this will, in effect, render FileZilla completely useless without server modifications.

Whilst you can argue that progress is necessary and improvements in security are a good thing, many users are simply unable to make the necessary modifications with immediate effect and anyone with any urgent requirement to use the program will be massively inconvenienced.

In my experience, 3.10.0 is as effective at managing a file server as a pen and paper, as connecting has become an impossibility. There are servers I work on that cannot be modified, at least in any reasonable time scale, and therefore installing 3.9.05 was my only option.

So, to anyone experiencing this problem who cannot "fix" every single one of the servers they require, the solution is to un-install 3.10.0 and install an older version if you are fortunate enough to have saved one. Or use a different program

botg wrote:

PTCO wrote:I followed BE55Roberts' advice, and it worked. When I contacted Bluehost to verify, Bluehost first suggested I select "Plain FTP" instead of "FTP over TLS", when I informed support of BE55Roberts' solution, he told me to do that.

Admins - is this an appropriate way to fix this?

No, it is only a workaround. The appropriate way to fix this is for the server administrators to fix their server.

Perhaps a better word for it would be "customization." There was nothing wrong with the server; it was doing what it was designed to do. The Web Hosting companies have to support both "Plain FTP" and "FTP over TLS" protocols. And they do, but you have to customize your account to enable the secure protocol. In my case, that was simply using the Control Panel interface to enable the secure protocol (i.e. Manage SSH access.) I recommend that others implement the same customization, then the Server and FileZilla 3.10.0 will get along.

You are completely wrong. What you did enable IS NOT FTP over TLS. You enabled SFTP/SSH, a completely different protocol, and you are actually lucky that your hoster supports it. Many others might not support SFTP (but it doesn't hurt to try since it is still better than plain FTP). The FTP over TLS (FTPS Explicit) support of the server is broken, it is what FileZilla now uses as default.

Fact #1: The only thing changed is that FTP over TLS is now default. You can still re-select plain FTP in the Site Manager. FTP over TLS is not forced.
Fact #2: FileZilla will try FTP over TLS only if the server announces support for it. Not FileZilla's fault if the server cannot fulfill its claims.

So you approach a bridge and the sign reads: "Up to 4.5t", and you cross with your 3t vehicle. The bridge collapses. In your logic the fault lies with the vehicle (FileZilla), but in reality it is the bridge's (server's) fault because it did announce something it can't actually support.