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.

I’ve reverted to 3.9.0.6 while waiting for my Web host to deal with the server. In the meantime, is there a way to get rid of the update window that pops up each time I open FileZilla?

Hey, Tim,

I really appreciate the huge amount of quality work you have put into Filezilla over the years, but you are missing something in these postings.

What you say about hosting services needing to clean up their servers is right on, but the fact remains that your new option in 3.10 to ignore a bad certificate DOES NOT WORK!

You can probably fix the ability to bypass a bad certificate rather easily. True, doing so is a bad, albeit needed, workaround.

The Godaddy customer service rep who helped me with this problem spoke unrelentingly in the twisted double talk of a very glib alcohol addict. Her twisted mind insisted that VOIP and insufficient bandwidth were my problem!!! Unlike you, Tim, Godaddy has to concurrently fix both some techies with addictive personalities and the servers maintained by them - a big task, but one which Godaddy must face.

With the new version (3.10.0) :
"
Statut : Résolution de l'adresse de genealogie-pyrenees.fr
Statut : Connexion à 109.234.161.25:21...
Statut : Connexion établie, attente du message d'accueil...
Statut : Initialisation de TLS...
Statut : Vérification du certificat...
Statut : Connexion TLS établie.
Statut : Le serveur ne supporte pas les caractères non-ASCII.
Statut : Connecté
Statut : Récupération du contenu du dossier...
Commande : PWD
Réponse : 257 "/" is your current location
Commande : TYPE I
Réponse : 200 TYPE is now 8-bit binary
Commande : PASV
Réponse : 227 Entering Passive Mode (109,234,161,25,247,60)
Commande : MLSD
Erreur : Délai d'attente expiré
Erreur : Impossible de récupérer le contenu du dossier
"

What I have to do in order to work again with FileZilla ?

Bonsoir à tous.

I have removed Filezilla v3.10.0 from my computer and I put again Filezilla v3.9.0.5

=> It's OK now and I'll work with the new version when the problem will be resolved.

With FileZilla v3.9.0.5 :

Statut : Résolution de l'adresse de genealogie-pyrenees.fr
Statut : Connexion à 109.234.161.25:21...
Statut : Connexion établie, attente du message d'accueil...
Réponse : 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Réponse : 220-You are user number 1 of 60 allowed.
Réponse : 220-Local time is now 02:12. Server port: 21.
Réponse : 220-This is a private system - No anonymous login
Réponse : 220-IPv6 connections are also welcome on this server.
Réponse : 220 You will be disconnected after 15 minutes of inactivity.
Commande : USER *********** (I change the name of the user)
Réponse : 331 User *********** OK. Password required (I change the name of the user)
Commande : PASS **********
Réponse : 230-Your bandwidth usage is restricted
Réponse : 230 OK. Current restricted directory is /
Commande : SYST
Réponse : 215 UNIX Type: L8
Commande : FEAT
Réponse : 211-Extensions supported:
Réponse : EPRT
Réponse : IDLE
Réponse : MDTM
Réponse : SIZE
Réponse : MFMT
Réponse : REST STREAM
Réponse : MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Réponse : MLSD
Réponse : AUTH TLS
Réponse : PBSZ
Réponse : PROT
Réponse : TVFS
Réponse : ESTA
Réponse : PASV
Réponse : EPSV
Réponse : SPSV
Réponse : ESTP
Réponse : 211 End.
Statut : Le serveur ne supporte pas les caractères non-ASCII.
Statut : Connecté
Statut : Récupération du contenu du dossier...
Commande : PWD
Réponse : 257 "/" is your current location
Commande : TYPE I
Réponse : 200 TYPE is now 8-bit binary
Commande : PASV
Réponse : 227 Entering Passive Mode (109,234,161,25,146,199)
Commande : MLSD
Réponse : 150 Accepted data connection
Réponse : 226-Options: -a -l
Réponse : 226 20 matches total
Statut : Contenu du dossier affiché avec succès

I can work again with FileZilla !!!!

cedial wrote:the fact remains that your new option in 3.10 to ignore a bad certificate DOES NOT WORK!

This is intentional, bad certificates (ie. expired) cannot be ignored. There has and never will be an option to permanently accept these.

The Godaddy customer service rep who helped me with this problem spoke unrelentingly in the twisted double talk of a very glib alcohol addict. Her twisted mind insisted that VOIP and insufficient bandwidth were my problem!!!

I agree, VOIP is a problem. POTS is better in every way.

Hi there, and big thanks for this useful tool. I use it many years now. Unfortunately for first time i have roll back version.

I use it for many (about 60-70) domains so i don't have the time to do all those settings ..


Anyway, my opinion is the option "FTP over TLS" must to be optional and not default.

Thanks,
Demetris

botg wrote:

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.

In cave-person days the FileZilla approach would be to seal up everyone's cave as soon as some houses had been built. Basically FileZilla chooses to disconnect people from their hosting services until those people can convince the services to update. That is simply not a "real world" solution. It's as practical as asking Honda to change the dimensions of their cars to fit my "updated" floor mats.Thankfully FZ version 3.9.0.6 works fine and is stable, and there are other ways to FTP to a server.

I have the same issue and reverting to 3.7.4.1 (my last saved installer) saved my day.

If 3.10 defaulted to regular FTP would that fix others needs? Perhaps with a pop-up that TLS is preferred, and why, and what to do if it does not work?

I will not try it again until I read more about the issue so many of us seem to have and some feel there is a workable resolution. I have emailed my host. I do not expect them to do much about it for me. Maybe I will be surprised.

~Bob

someguy321 wrote:In cave-person days the FileZilla approach would be to seal up everyone's cave as soon as some houses had been built. Basically FileZilla chooses to disconnect people from their hosting services until those people can convince the services to update. That is simply not a "real world" solution. It's as practical as asking Honda to change the dimensions of their cars to fit my "updated" floor mats.Thankfully FZ version 3.9.0.6 works fine and is stable, and there are other ways to FTP to a server.

Your analogy is flawed. It actually goes like this:

FileZilla: "Do you have a house?"
Lying caveman: "Yes!"

Two solutions for this problem: Either the caveman actually builds a house or should instead answer no when asked whether he has a house.

Anyone hosting with GoDaddy you can refer to their support page - https://support.godaddy.com/help/articl ... s-explicit

I guess I'll have to live in a safe, working cave, instead of upgrading to a faulty, perhaps more secure, house.

BTW, my last working install file is 3.5.3. Those of you with more recent installs are lucky!

My host replied:

Thank you for contacting support. We do not offer FTPS or FTP via TLS so the default connection configuration will fail. You will need to disable that option or consider using SFTP, https://my.hostmonster.com/cgi/help/248

I think you might have lost a little touch with your users and their hosts. Not everyone has this. At least, if you believe it to be a benefit, make it optional. But something that has worked for years broke and started more conversations here than it is worth. IF it had been an option and with a better explanation, it might be welcomed. Its like someone required IPV6, which most will not understand and many (such as I) have no access to right now.

~Bob

At least, if you believe it to be a benefit, make it optional. But something that has worked for years broke and started more conversations here than it is worth. IF it had been an option and with a better explanation, it might be welcomed.

You might want to check Site Manager again. FileZilla does not force FTPES, it uses FTPES because the server announces support for FTPES. If the hoster's FTP server does not support FTP over TLS, it MUST reply to the AUTH command with a 5xx (error).

All OK, thanks!