Downloaded new update, now directory listings don't show.

[Allen]

I've been happily using Filezilla for over a year now with no problems. Just an hour or so ago 4/27/09 I downloaded the latest update you sent. Now nothing shows up in the directory listing. It is connecting just fine, but no directory listing, even though the message says directory listing successful. I've changed nothing but downloading the new update. Any suggestions?

[Tim Kosse]

Please enable "Show raw directory listings" in the settings dialog and attach a complete, unmodified log.

[usrhlp]

I too have this bug and i think i know what is wrong.

FTP servers that run the Pure-FTPd [TLS] software do not display their contents.

Before upgrading to 3.2.4.1 the directories were full and worked fine but since upgrading the directories are empty.

In order to see if the files had been deleted i checked the directories though cpanel and the files i hoped to see were there.

I restarted filezilla logged into the server and the directory was empty even though Cpanel clearly shows files exist and the website works without a problem.

I have tried different servers and some servers display files and others dont. even though all the servers do contain files filezilla still showed some as empty.

Here is a run down

Status: Connecting to 207.44.176.69:21...
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [TLS] ----------

the directories display as blank.

Status: Connecting to 66.147.242.98:21...
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [TLS] ----------

This server displays as blank.

Status: Connecting to 92.48.108.230:21...
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [TLS] ----------

This server displays as blank

Status: Connecting to 62.128.198.22:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.2.9 Server (ProFTPD)

This server works as normal.

Status: Connecting to 66.40.52.69:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.2.9 Server (ProFTPD) [1.1.64]

This server displays as normal.

This suggests there is an incompatibility between Pure-FTPd [TLS] and the new version of filezilla.

[Tim Kosse]

Requested information have not been provided yet.

[usrhlp]

Status: Connection established, waiting for welcome message...
Trace: CFtpControlSocket::OnReceive()
Response: 220---------- Welcome to Pure-FTPd [TLS] ----------
Response: 220-You are user number 3 of 50 allowed.
Response: 220-Local time is now 17:03. Server port: 21.
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 15 minutes of inactivity.
Trace: CFtpControlSocket::SendNextCommand()
Command: USER user
Trace: CFtpControlSocket::OnReceive()
Response: 331 User user OK. Password required
Trace: CFtpControlSocket::SendNextCommand()
Command: PASS
Trace: CFtpControlSocket::OnReceive()
Response: 230-User userhas group access to: user
Response: 230 OK. Current restricted directory is /
Status: Connected
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Retrieving directory listing...
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::ChangeDirSend()
Command: PWD
Trace: CFtpControlSocket::OnReceive()
Response: 257 "/" is your current location
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Directory listing successful

*Directory shows as empty*

Is that what you are looking for?

[Tim Kosse]

Log does not show a listing attempt. Please post a log where a listing is fetched.

[usrhlp]

Here is another log from another site that has a failed listing.

Status: Connection established, waiting for welcome message...
Trace: CFtpControlSocket::OnReceive()
Response: 220---------- Welcome to Pure-FTPd [TLS] ----------
Response: 220-You are user number 1 of 50 allowed.
Response: 220-Local time is now 11:07. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220 You will be disconnected after 15 minutes of inactivity.
Trace: CFtpControlSocket::SendNextCommand()
Command: USER user
Trace: CFtpControlSocket::OnReceive()
Response: 331 User user OK. Password required
Trace: CFtpControlSocket::SendNextCommand()
Command: PASS *
Trace: CFtpControlSocket::OnReceive()
Response: 230-User user has group access to: runningr
Response: 230 OK. Current restricted directory is /
Status: Connected
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Retrieving directory listing...
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::ChangeDirSend()
Command: PWD
Trace: CFtpControlSocket::OnReceive()
Response: 257 "/" is your current location
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: TYPE I
Trace: CFtpControlSocket::OnReceive()
Response: 200 TYPE is now 8-bit binary
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: PASV
Trace: CFtpControlSocket::OnReceive()
Response: 227 Entering Passive Mode (207,44,176,69,94,51)
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: MLSD
Trace: CTransferSocket::OnConnect
Trace: CFtpControlSocket::OnReceive()
Response: 150 Accepted data connection
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Trace: CTransferSocket::OnClose(0)
Trace: CTransferSocket::TransferEnd(1)
Trace: CFtpControlSocket::TransferEnd()
Trace: CFtpControlSocket::OnReceive()
Response: 226-ASCII
Response: 226-Options: -a -l
Response: 226 27 matches total
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Directory listing successful

This is a listing from a working site.

Status: Connection established, waiting for welcome message...
Trace: CFtpControlSocket::OnReceive()
Response: 220 ProFTPD 1.2.9 Server (ProFTPD) [1.1.64]
Trace: CFtpControlSocket::SendNextCommand()
Command: USER user
Trace: CFtpControlSocket::OnReceive()
Response: 331 Password required for user.
Trace: CFtpControlSocket::SendNextCommand()
Command: PASS *
Trace: CFtpControlSocket::OnReceive()
Response: 230 User user logged in.
Status: Connected
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Retrieving directory listing...
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::ChangeDirSend()
Command: PWD
Trace: CFtpControlSocket::OnReceive()
Response: 257 "/" is current directory.
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: TYPE I
Trace: CFtpControlSocket::OnReceive()
Response: 200 Type set to I
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: PASV
Trace: CFtpControlSocket::OnReceive()
Response: 227 Entering Passive Mode (66,40,52,69,190,103).
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: LIST
Trace: CTransferSocket::OnConnect
Trace: CFtpControlSocket::OnReceive()
Response: 150 Opening ASCII mode data connection for file list
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Listing: drwxr-xr-x 5 313913 vuser 4096 Jan 12 13:07 a1-storage.co.uk
Trace: CTransferSocket::TransferEnd(1)
Trace: CFtpControlSocket::TransferEnd()
Trace: CFtpControlSocket::OnReceive()
Response: 226 Transfer complete.
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Directory listing successful

[Tim Kosse]

Recent versions of FileZilla use MLSD, a better alternative to LIST since MLSD listings are standardized, LIST listings aren't.

The problem at hand is not a problem with FileZilla, it's the server that does return empty listings. Note that FileZilla only uses MLSD if the server advertises MLSD support. Please contact the server administrator so that he can upgrade to a proper server that supports MLSD and actually works.

As temporary workaround refrain from using that server until it gets fixed.

[usrhlp]

"As temporary workaround refrain from using that server until it gets fixed."
Not really a work around is it?

That's like saying "swine flu pandemic exists....fix = dont breathe until pandemic over".

Is there any way for the user to select between LIST and MLSD until the admins of the servers which show this problem and that the users have no control or power over upgrade to a MLSD supporting server?

[usrhlp]

One fix is to downgrade your filezilla to 3.1.3.1 obtainable here.

​https://www.ohloh.net/p/filezilla/download?package=FileZilla+Client+Stable+releases&release=3.1.3.1

Install it into a new directory so you dont lose the new version of the software. That way you can still access the LIST servers and the MLSD servers at the same time.

[Murray Collingwood]

Hi folks

I clicked 'Reopen' in the hope that you can at least point me towards a solution as opposed to leaving this problem in the dark.

I am experiencing the same issue described above - exactly the same.

My server is Debian-lenny with recent patches applied. The latest FTPD server etc.
I can't see find anything to install of update that would indicate support for MLSD - perhaps you can point me at something. However, as it stands I would suggest that the FTPD server I'm running is not advertising support for MLSD and therefore FileZilla should not be asking for it.

Also, I have down-graded FileZille to 3.1.1.1 in order to test earlier versions (pre-MLSD) however this has not made any difference to the result.

On this same server I have FTP sites that do display listings and sites that will not display listings (although I can see the files are there when I login).

The different between the two sites is that the ones that don't list I am using 'ftpchroot' to restrict the user to named directory. The sites that work normally are not using 'ftpchroot'.

However it is disconcerting that FileZilla does not show a directory listing for these restricted logins. It should be. In these restricted logins I can upload a file using FileZilla and the file is uploaded happily, and when I do so the file appears in the directory list, however if I refresh the view the file disappears. Clearly this is an issue with processing the output from the directory list on the server... or is it the server failing to return a directory list... which is it?

How can I check whether the server is not returning a list, or it is returning a list that FileZilla is not parsing?

Cheers
Murray

[Murray Collingwood]

Okay - don't worry. This is a bug on the server with FTPD and the use of ftpchroot. I tested with gFTP and got exactly the same response. I'm chasing this as a bug with Debian now.