Opened 11 years ago

Last modified 11 years ago

#3471 closed Bug report

Won't open large directories anymore

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

Description

I've been using Filezilla for awhile. On earlier versions, I was able to open folders on my website no matter the size. However, I updated to version 3.0.8.1, and now I can't open large folders. It'll just try forever and then finally timeout and disconnect. I just updated to 3.0.9.1 today, but it still does the same thing. This has happened before when I updated from version 2 a while back. I'm pretty suspicious and cautious about updating filezilla, and I should have been more this time. I haven't been able to update my website since I updated this time again. Please help.

Change History (6)

comment:1 Changed 11 years ago by Alexander Schuch

Please backup your FileZilla configuration ("\Documents and Settings\<username>\Application Data\FileZilla" or "~/.filezilla") and use latest 3.0.7.x version of FileZilla. Does the problem go away magically? If yes, it sounds like a bug in FileZilla, if not, you may have changed something in your configuration.

Can you please provide a message log of at least verbose log level, better debug log level? And which platform/operating system are you using?

comment:2 Changed 11 years ago by decoydoyle

I'm using Windows XP.

I'm not sure if this is what you want, but here it is:

Status: Resolving IP-Address for www.decoy.cc
Status: Connecting to 203.22.204.117:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.2.9 Server (ProFTPD) [tonga.globat.com]
Command: USER doyle
Response: 331 Password required for doyle.
Command: PASS
Response: 230 User doyle logged in.
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: 211 End
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (203,22,204,117,234,169).
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD httpdocs
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/httpdocs" is current directory.
Command: PASV
Response: 227 Entering Passive Mode (203,22,204,117,234,97).
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Response: 226 Transfer complete.
Status: Calculating timezone offset of server...
Command: MDTM index.html
Response: 213 20080126133127
Status: Timezone offsets: Server: 0 seconds. Local: 32400 seconds. Difference: 32400 seconds.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD video
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/httpdocs/video" is current directory.
Command: PASV
Response: 227 Entering Passive Mode (203,22,204,117,234,154).
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD 2007
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/httpdocs/video/2007" is current directory.
Command: PASV
Response: 227 Entering Passive Mode (203,22,204,117,234,128).
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Error: Connection timed out
Error: Failed to retrieve directory listing

Thanks.

comment:3 Changed 11 years ago by Tim Kosse

Most likely just a very slow server. Increase the timeout value in the client's settings and try again.

comment:4 Changed 11 years ago by decoydoyle

That wouldn't explain how it was working perfectly before updating, but then not opening large directories at all directly after updating. It has worked a few times since this, but it is very rare. I did however, increase the timeout value and even went to infinite. That didn't work. It just made it timeout for however long I put it.

comment:5 Changed 11 years ago by Tim Kosse

Your configuration seems to be improper. Please run the network
configuration wizard and follow its instructions.

As long as the test at the end of the wizard fails, your
configuration is not correct.

Reopen only if the test succeeds and the problem did not go away.

comment:6 Changed 11 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Note: See TracTickets for help on using tickets.