Updated To Version 3.10.0 Now Receiving Errors

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Message
Author
phop
500 Command not understood
Posts: 1
Joined: 2015-03-26 07:06
First name: Phil
Last name: Soth

Re: Updated To Version 3.10.0 Now Receiving Errors

#196 Post by phop » 2015-03-26 07:20

I am new to FileZilla Forum and came here primarily because of the 3.10 upgrade. I am currently at 3.10.1.1, but have not installed 3.10.2-rc1, 3.10.2-rc2, or 3.10.2, even though they are in my update "Check for Updates" when I open FileZilla. My server is register.com and the technician I talked with this evening told me that "Explicit FTP over TLS" isn't really all that important as my login and password offer sufficient security. If that's the case, why not simply use "plain FTP (insecure)?" The register.com people showed little interest in pursuing the issue any further.

My question: Will I run into problems updating to the latest version(s), or should I stay where I am? By the way, ftptest.net times out without giving any results when I run it against my register.com account.

Please advise.

(03-27-2015 12:05 AM) I am editing my earlier post. In conversation with another tech at the server company, come to find out that security level will depend on which port is being used. Thus, I have upgraded to 3.10.2, and logged in using the "secure" port and everything works fine. Too bad not all techs have a complete skillset.
Last edited by phop on 2015-03-27 07:06, edited 1 time in total.

User avatar
boco
Contributor
Posts: 24651
Joined: 2006-05-01 03:28
Location: Germany

Re: Updated To Version 3.10.0 Now Receiving Errors

#197 Post by boco » 2015-03-26 12:07

First: That "technician" is an *****. Using plain FTP transfers everything including passwords in clear text, easily readable for everyone along the way who wants it.
FTP over TLS provides end-to-end encryption against man-in-the-middle attacks and surveillance, something many hosters (and the three-letter-agencies in the back) are not particular interested in. I cannot think of another reason why they are holding back.

If you run an older version with default settings, you use Plain FTP anyway. Even with the new version forced to Plain you would not be any worse (as if it could get worse than Plain FTP). And you stay supported.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

dorikond
500 Command not understood
Posts: 3
Joined: 2015-04-22 12:43
First name: dori
Last name: kond

Re: Updated To Version 3.10.0 Now Receiving Errors

#198 Post by dorikond » 2015-04-22 13:02

Please can help me someone?
When I try to connect i see the text below:
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server

dorikond
500 Command not understood
Posts: 3
Joined: 2015-04-22 12:43
First name: dori
Last name: kond

Re: Updated To Version 3.10.0 Now Receiving Errors

#199 Post by dorikond » 2015-04-22 13:04

Please can help me someone?
When I try to connect i see the text below:
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server

User avatar
boco
Contributor
Posts: 24651
Joined: 2006-05-01 03:28
Location: Germany

Re: Updated To Version 3.10.0 Now Receiving Errors

#200 Post by boco » 2015-04-22 17:41

There doesn't seem to be any FTP server at that address...
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

dorikond
500 Command not understood
Posts: 3
Joined: 2015-04-22 12:43
First name: dori
Last name: kond

Re: Updated To Version 3.10.0 Now Receiving Errors

#201 Post by dorikond » 2015-04-22 19:20

Now i see this message. What to do ?
Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Status: Connection established, waiting for welcome message...
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Could not connect to server
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.powernews24.com
Status: Connecting to 72.167.191.69:21...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Could not connect to server

User avatar
boco
Contributor
Posts: 24651
Joined: 2006-05-01 03:28
Location: Germany

Re: Updated To Version 3.10.0 Now Receiving Errors

#202 Post by boco » 2015-04-22 20:41

You must ask the company hosting your website if they offer FTP access (run an FTP server) and what's the correct login data if they do. At the moment it looks like there is no one listening at the other side, so you won't get any connection.

FTP needs an FTP server listening at the target address. You can't connect to web servers with FileZilla.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

tomrogers
500 Command not understood
Posts: 2
Joined: 2015-05-13 19:21
First name: Tom
Last name: Rogers

Re: Updated To Version 3.10.0 Now Receiving Errors

#203 Post by tomrogers » 2015-05-13 19:30

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.
This is laughable. What you're saying is that everyone else has to fix their servers so FileZilla will work.

This morning I upgraded to 3.5.3, and now can not connect to servers at VPS.net or Miva.com. As a result, I can't access over 20 websites.

The message I get is:

Response: 530 Login authentication failed
Error: Critical error
Error: Could not connect to server

User avatar
boco
Contributor
Posts: 24651
Joined: 2006-05-01 03:28
Location: Germany

Re: Updated To Version 3.10.0 Now Receiving Errors

#204 Post by boco » 2015-05-13 21:49

What you're saying is that everyone else has to fix their servers so FileZilla will work.
No, not everyone else! Only the administrators of wrongly configured servers have to, which will fix it for all their users.
This morning I upgraded to 3.5.3, and now can not connect to servers at VPS.net or Miva.com. As a result, I can't access over 20 websites.
Do you mean 3.10.3?
530 Login authentication failed
Do you use the Site Manager? If you re-enter the password of one entry, then press OK (forcing a re-save), then connect using that entry again, are you able to connect?
Usually 530 errors do mean incorrect login data, but as all servers fail now it might be something different...
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

tomrogers
500 Command not understood
Posts: 2
Joined: 2015-05-13 19:21
First name: Tom
Last name: Rogers

Re: Updated To Version 3.10.0 Now Receiving Errors

#205 Post by tomrogers » 2015-05-14 12:37

That's odd. I was prompted to upgrade, but that was obviously an old version. I found the new version 3.10.2 at SourceForge, and got that working, but still got the same errors:

Response: 530 Login authentication failed
Error: Critical error: Could not connect to server

You were right. When I pasted in the passwords, it connected!
Not sure why that occurred. The passwords for every account were 2 to 3 times longer than they should have been.

Thanks!!

uic88tz
504 Command not implemented
Posts: 8
Joined: 2015-05-14 14:32

Re: Updated To Version 3.10.0 Now Receiving Errors

#206 Post by uic88tz » 2015-05-14 14:42

Just updated to new version. I did the online FTP tester, which is good.

Your server is working and assorted routers/firewalls have been correctly configured for plain basic FTP as performed by this test. However there have been warnings about compatibility issues, not all users will be able to use your server.

Status: Resolving address of 69.195.124.61
Status: Connecting to 69.195.124.61
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Reply: 220-You are user number 3 of 1000 allowed.
Reply: 220-Local time is now 08:33. Server port: 21.
Reply: 220-This is a private system - No anonymous login
Reply: 220-IPv6 connections are also welcome on this server.
Reply: 220 You will be disconnected after 15 minutes of inactivity.
Command: CLNT https://ftptest.net on behalf of 98.20.251.112
Reply: 530 You aren't logged in
Command: USER uniteeg3
Reply: 331 User uniteeg3 OK. Password required
Command: PASS ************
Reply: 230 OK. Current restricted directory is /
Command: SYST
Reply: 215 UNIX Type: L8
Command: FEAT
Reply: 211-Extensions supported:
Reply: EPRT
Reply: IDLE
Reply: MDTM
Reply: SIZE
Reply: MFMT
Reply: REST STREAM
Reply: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Reply: MLSD
Reply: AUTH TLS
Reply: PBSZ
Reply: PROT
Reply: ESTA
Reply: PASV
Reply: EPSV
Reply: SPSV
Reply: ESTP
Reply: 211 End.
Command: PWD
Reply: 257 "/" is your current location
Status: Current path is /
Command: TYPE I
Reply: 200 TYPE is now 8-bit binary
Command: PASV
Reply: 227 Entering Passive Mode (69,195,124,61,172,139)
Command: MLSD
Status: Data connection established.
Reply: 150 Accepted data connection
Listing: type=cdir;sizd=4096;modify=20150421201055;UNIX.mode=0710;UNIX.uid=2202;UNIX.gid=12;unique=821g72e0001; .
Listing: type=pdir;sizd=4096;modify=20150421201055;UNIX.mode=0710;UNIX.uid=2202;UNIX.gid=12;unique=821g72e0001; ..
Listing: type=file;size=63;modify=20141029184224;UNIX.mode=0600;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e00b6; .bash_history
Listing: type=file;size=18;modify=20130718131903;UNIX.mode=0644;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e0002; .bash_logout
Listing: type=file;size=191;modify=20030624163219;UNIX.mode=0644;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e0003; .bash_profile
Listing: type=file;size=175;modify=20120522221830;UNIX.mode=0644;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e0006; .bashrc
Listing: type=file;size=23;modify=20141016141717;UNIX.mode=0600;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e001f; .contactemail
Listing: type=dir;sizd=4096;modify=20141029182255;UNIX.mode=0700;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e001d; .cpanel
Listing: type=dir;sizd=4096;modify=20130614152812;UNIX.mode=0755;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e0015; .cpanel-datastore
Listing: type=file;size=26;modify=20141029181507;UNIX.mode=0644;UNIX.uid=2202;UNIX.gid=2202;unique=821g72e011f; .dns
Reply: 226-Options: -a -l
Reply: 226 31 matches total
Status: Skipped display of 21 listing lines
Status: Success

I still cannot get logged in to Filezilla. This is what I get when I try.

Status: Connecting to 69.195.124.61: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...
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 (69,195,124,61,162,43)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing


Can someone please help me?

Thank you so much!!!!

User avatar
botg
Site Admin
Posts: 32336
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Updated To Version 3.10.0 Now Receiving Errors

#207 Post by botg » 2015-05-14 19:10

@uic88tz: There is probably a firewall or NAT router on your end of the connection that is interfering with the transfer.

AnthonyJKenn
500 Command not understood
Posts: 1
Joined: 2015-05-16 07:16
First name: Anthony
Last name: Kennerson

Re: Updated To Version 3.10.0 Now Receiving Errors

#208 Post by AnthonyJKenn » 2015-05-16 07:37

Hello....I have also had some issues with Filezilla's FTP over TLS errors using my HostGator.com reseller account, but I was able to resolve it just now through this alternative:

1) Enabling SSH (Secure Shell) access through the webhost. I can't speak for others, but HostGator automatically allows SSH access for one account (reseller or shared) for free, and offers SSH access for other accounts for a one-time fee.

2) Registering the FTP through Filezilla: change the protocol to "SFTP -- SSH File Transfer Protocol" and reset the port to "2222" rather than "22" (the standard for regular FTP). Other values are the same.

It turns out that most of the webhosts who do not use FTP over TLS can use SFTP, which uses a slightly different standard. If your webhost can use SFTP, it should be able to be set up under Filezilla to run securely. It's just a matter of having your webhost enable SSH.

That for me solved my problem; it may solve yours.

User avatar
boco
Contributor
Posts: 24651
Joined: 2006-05-01 03:28
Location: Germany

Re: Updated To Version 3.10.0 Now Receiving Errors

#209 Post by boco » 2015-05-16 08:29

It turns out that most of the webhosts who do not use FTP over TLS can use SFTP, which uses a slightly different standard.
Replace "slightly different" with "completely different". Apart from the similar name and same purpose both protocols have nothing in common.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

TN-Notebooks
500 Command not understood
Posts: 2
Joined: 2015-05-17 11:46
First name: Thomas
Last name: Neumann

Re: Updated To Version 3.10.0 Now Receiving Errors

#210 Post by TN-Notebooks » 2015-05-17 12:04

Hallo

i have a Problem with FZ 3.10.3
at my Server 2008R2 Foundation had been a bad HDD in Raid5
So i installed Acronis 11.5 Backup to Backup the system and fixed the problems by Installing new HDD and recover
System works

But
After that i can not access by Filezilla from all other computers
Every other FTP Client works. Remote Acess works.
There had been no changes on the Computers where Filezilla is installed

So the Problem is on the Server and affects only Filezilla !
The Solution i want to find the Problem on the Server and not change Settings in Filezilla ... before everything worked perfect.

Microsoft Essentials and Firewall had been disabled - no help
I attache a Log .... can you Help ?? Thank you

Status: Auflösen der IP-Adresse für tn-notebooks.webhop.me
Status: Verbinde mit 79.254.3.208:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Status: Initialisiere TLS...
Status: Überprüfe Zertifikat...
Status: TLS-Verbindung hergestellt.
Status: Verbunden
Status: Empfange Verzeichnisinhalt...
Status: Vom Server gesendete Adresse für den Passiv-Modus ist nicht routingfähig. Benutze stattdessen die Serveradresse.
Befehl: LIST
Antwort: 150 Opening BINARY mode data connection.
Fehler: Zeitüberschreitung der Verbindung nach 20 Sekunden Inaktivität
Fehler: Verzeichnisinhalt konnte nicht empfangen werden

---------------------------------------------------------------------------------------------

Test log
Status: Resolving address of tn-notebooks.webhop.me
Status: Connecting to 79.254.3.208
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220 Microsoft FTP Service
Command: CLNT https://ftptest.net on behalf of 79.254.3.208
Reply: 500 'CLNT https://ftptest.net on behalf of 79.254.3.208': command not understood.
Command: AUTH TLS
Reply: 234 AUTH command ok. Expecting TLS Negotiation.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Command: USER Administrator
Reply: 331 Password required for Administrator.
Command: PASS *****************
Reply: 230 User logged in.
Command: SYST
Reply: 215 Windows_NT
Command: FEAT
Reply: 211-Extended features supported:
Reply: LANG EN*
Reply: UTF8
Reply: AUTH TLS;TLS-C;SSL;TLS-P;
Reply: PBSZ
Reply: PROT C;P;
Reply: CCC
Reply: HOST
Reply: SIZE
Reply: MDTM
Reply: REST STREAM
Reply: 211 END
Warning: The server does not indicate MLSD support. MLSD uses a well-specified listing format. Without MLSD, directory listings have to be obtained using LIST which uses an unspecified output format.
Command: PBSZ 0
Reply: 200 PBSZ command successful.
Command: PROT P
Reply: 200 PROT command successful.
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I.
Command: PASV
Reply: 227 Entering Passive Mode (192,168,178,28,202,111).
Error: Server returned unroutable private IP address in PASV reply
Results
Error: Server returned unroutable private IP address in PASV reply
Make sure the server is configured to allow passive mode connections.
If the server is behind a NAT router, make sure the server knows its external IP address.
The range of ports used for passive mode must be opened in all involved firewalls.
The range of ports used for passive mode must be forwarded by all involved NAT routers.
Try uninstalling all firewalls and plug your computer directly into your modem, thus bypassing the router.

Locked