Opened 15 years ago

Last modified 6 years ago

#795 closed Bug report

Filezilla shows empty dir listing for some sites

Reported by: al__capone_ Owned by: Alexander Schuch
Priority: normal Component: Other
Keywords: Cc: al__capone_, Alexander Schuch, Tim Kosse, digit48
Component version: Operating system type:
Operating system version:

Description

this is really weird !
-Filezilla Server is running.
CuteFTP client can connect (PASV) and list and work with it
so can many otyher clients
FTP client in command line of W2K/XP works too.

Filezilla (client) however, *DOES NOT* show any files,
directorys and it does NOT show any error after
recieving directory listing.

this is at least true for 2.2.9 and 2.2.10 for windows.

Please fix :)

BTW:to whoever looks into this - feel free to contact
me and i will give you and IP and account to the
Filezilla server - so you can reproduce thei problem in
no-time.

Regards

Change History (14)

comment:1 Changed 15 years ago by Tim Kosse

Are you using any routers, firewalls or virus scanners? If
yes, please try to connect without the router and uninstall
any firewalls and virus scanners.

comment:2 Changed 15 years ago by al__capone_

it is not that simple - please read again and understand
this time: *any* OTHER FTP client I have tried works
perfectly , so there is no way this can be blamed on
router/FW etc.

comment:3 Changed 15 years ago by Tim Kosse

Did you already try to toggle the passive mode setting in
the settings dialog?

comment:4 Changed 15 years ago by al__capone_

of course I did.
and this server is only supposed to work in PASV mode.
any serious developer that understands this is more than
welcome to contact me for IP & login information - then you
can verify yourself that "any" other, (even command line)
FTP client handles this site - EXCEPT Filezilla.

comment:5 Changed 15 years ago by Tim Kosse

Please mail the login information to codesquid@…

comment:6 Changed 15 years ago by digit48

This seems to occur with the latest version of Filezilla
(2.2.12c) and any version >= 0.9.4 on the server.

The admin interface says:
150 Opening data channel for directory list.
425 Can't open data connection.

I am behind a router.

comment:7 Changed 13 years ago by Alexander Schuch

Does this problem still occur with current versions of FileZilla 2 (or FileZilla 3 beta)
and FileZilla Server?

comment:8 Changed 13 years ago by Alexander Schuch

As there is no way to test this without the help of the
original/any bug reporter, I am putting this report into
pending state. It will be closed automatically in 14 days if
there is no answer.

comment:9 Changed 13 years ago by digit48

I carried out a few tests with as much of the same setup as
possible today. (My computer's physical location has changed
since, though, so it cannot be exact.) The same problem
presented itself with server 0.9.19 beta, client 2.2.18. I
have not tested the latest client yet, though, I will try it
later.

comment:10 Changed 13 years ago by Alexander Schuch

Can you please enable raw directory listing (in the debug settings somewhere) and post the
logs somewhere (in case you cannot add them to this tracker item).

comment:11 Changed 13 years ago by digit48

OK, the testing is not going well because I am behind some
kind of firewall (just stops on PORT command). It's not
mine, so I can't forward ports or try to turn it off, but I
am going to try to get permission from my network admin to
let me through.

comment:12 Changed 13 years ago by al__capone_

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).

comment:13 Changed 13 years ago by al__capone_

I have another FTP server now,and another IP, router, and ISP.
cannot reproduce it anymore, even with the older versions of
FileZilla.

the error were worked around using other clients. Today my
FTP works fine with filezilla, using similiar config.

sorry for late response, please close.

comment:14 Changed 13 years ago by Alexander Schuch

digit48: This bug will stay closed for now, but feel free to still post, if you can still
reproduce the problem mentioned.

Note: See TracTickets for help on using tickets.