Opened 7 years ago
Closed 7 years ago
#11564 closed Bug report (rejected)
cannot get directory listing
Reported by: | Allan braun | Owned by: | |
---|---|---|---|
Priority: | high | Component: | FileZilla Client |
Keywords: | Cc: | ||
Component version: | 3.32.0 | Operating system type: | Windows |
Operating system version: | Windows 10 |
Description
I can successfully use MS-Windows cmd FTP
I login and get this message
OK. Current restricted directory is /
I enter:
cd www
dir
I get the entire website listing
When I use FileZilla version 3.32.0
I get this error
Status: Resolving address of www.organizeyourlife.org
Status: Connecting to 204.27.63.50:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
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 (204,27,63,50,46,36)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Resolving address of www.organizeyourlife.org
Status: Connecting to 204.27.63.50:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
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 (204,27,63,50,147,5)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Many thanks for the workaroud, I can reproduce the issue and confirm that specifying "Only use plain FTP (insecure)" I can connect.
Maybe filezilla should have a policy of automatically jump to next encryption type before finally failing?
Thanks.
This fixed the problem
I changed the Encryption: option to "Only use plain FTP (insecure)".
This was required since my hosting company moved my website to a new server