Moderator: Project members
-
Sarge
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-17 04:30
- First name: Sargent
- Last name: Scott
Failed to retrieve directory listing
#1
Post
by Sarge » 2015-07-17 04:51
I keep getting «Failed to retrieve directory listing»
This only happened on the recent update.
How can I fix this?
-
botg
- Site Admin
- Posts: 34744
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
-
Contact:
Re: Failed to retrieve directory listing
#2
Post
by botg » 2015-07-17 08:58
Please post a complete Log.
-
Sarge
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-17 04:30
- First name: Sargent
- Last name: Scott
Re: Failed to retrieve directory listing
#3
Post
by Sarge » 2015-07-18 20:17
Sorry, its below:
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Resolving address of srv105.insty.me
Status: Connecting to 69.16.221.206: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: PORT 192,168,200,10,26,164
Response: 500 I won’t open a connection to 192.168.200.10 (only to 72.235.147.63)
Command: PASV
Response: 227 Entering Passive Mode (69,16,221,206,123,170)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
-
botg
- Site Admin
- Posts: 34744
- Joined: 2004-02-23 20:49
- First name: Tim
- Last name: Kosse
- Contact:
Re: Failed to retrieve directory listing
#4
Post
by botg » 2015-07-19 07:55
Two issues here.
You have configured your client to use active mode, yet you are behind a NAT router. Please configure both client and router according to the Network Configuration guide if you want to use active mode.
Also, it appears that some firewall is interfering with the connection, probably the server is behind some firewall or NAT router that isn’t configured for passive mode FTP. You can check your server’s configuration on https://ftptest.net/ . Contact your server administrator or server hosting provider for assistance to fix any server issues.
-
Sarge
- 500 Command not understood
- Posts: 3
- Joined: 2015-07-17 04:30
- First name: Sargent
- Last name: Scott
Re: Failed to retrieve directory listing
#5
Post
by Sarge » 2015-07-20 20:47
I tried to set up passive mode using the set up wizard, but not successful. This is all Greek to me.
How can I get back my old set up, before the last Filezilla update? Or can I just install an older Filezilla version?
-
boco
- Contributor
- Posts: 26451
- Joined: 2006-05-01 03:28
- Location: Germany
Re: Failed to retrieve directory listing
#6
Post
by boco » 2015-07-21 01:14
The Network test doesn’t test Passive mode as there’s nothing to test. Passive mode doesn’t require any client configuration, just set in in the Settings and call it a day.
Testing the server using https://ftptest.net is easy. Just use your normal login data like you would in FileZilla.
1. Set Protocol to «Explicit FTP over TLS», since that’s what FileZilla uses by default if the server announces support (most do).
2. If that fails, try «Plain FTP (Insecure)».
If 1. fails and 2. works, we have the typical case of a server not supporting FTP over TLS correctly. In that case you need to enter login data into FileZilla’s Site Manager (first icon) and set Encryption to Plain.
Please note that downgrading is not a supported use case. You might lose data and you do lose support.
### 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.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
After changing my dlink router with a Netgear d6000 I’m no longer able to connect to ftps via filezilla. The settings for ftp connections remained the same but after connecting to the server, Filezilla timeouts after 20 seconds of reading folders(nothing appears in the directory tree). Same problems with different ftps. I don’t know if it’s router related.
Edit: It’s not a timeout issue. Changing the timeout value doesn’t change the problem. It blocks when reading folders.
asked Mar 31, 2015 at 11:09
MutekingMuteking
3711 gold badge3 silver badges8 bronze badges
1
In my case
- Click Edit on Menu
- Click Settings
- Set Time Out to ‘0’
That’s it. It worked in my case.
Tried all the above mentioned methods but it wont make any change in my problem.
By just disabling the time out it worked.
Toto
16.2k46 gold badges29 silver badges39 bronze badges
answered Jun 9, 2018 at 9:18
GiriGiri
1711 silver badge2 bronze badges
0
- Open Site manager
- Click on “New site” button
- You need to change the Encryption to “Only use plain FTP (insecure)” and Logon type to Normal
- Enter host address, user name and password and click “Connect”
- Proceed as per the messages, you may need to enter the passwords again , enter it.
Click here to see the details with screenshots
answered Jul 12, 2016 at 12:03
RbGRbG
2772 silver badges3 bronze badges
5
-
Open FileZilla client application on your desktop. A new window will open for FileZilla.
-
Click Edit on menu bar and select Settings option.
-
Click Settings and a new small Settings window will open. In the left side of the Settings window there is a subsection called Select page, select the top option called Connection (by default it is selected when you open Settings window if it is not then select it manually). When you click on the connection link you will get an option to set timeout on the right side. In that Timeout section you will get an option to set timeout value from 0-599 seconds. Set this according to your need or you can disable this Timeout settings by settings its value to 0.
Jawa
3,57913 gold badges31 silver badges36 bronze badges
answered Mar 31, 2015 at 12:23
1
I had the same problem when I switched from a D-Link router to a Asus RT-AC68U.
My problems where solved by disabling the NAT Acceleration.
This description is for a Asus router but look for NAT Acceleration/Hardware acceleration or something like that, if you have another router.
- Login to the router
- In the left menu, under Advanced Settings, click the LAN button.
- Then click the Switch Control tab.
- Set NAT Acceleration to Disable.
answered Jul 9, 2015 at 20:11
2
This is how I fixed it:
Advanced -> NAT -> RIP CONFIG LIST -> Enable FTP
Insane
2,9116 gold badges26 silver badges49 bronze badges
answered Nov 17, 2015 at 0:08
- Open Site manager
- Click on “New site” button
- You need to change the Encryption to “Only use plain FTP (insecure)”
and Logon type to Normal - Enter host address(using ip is better
), user name and password and click “Connect” - Open transfer settings tab
- Change transfer mode from
defaulttoactive - Proceed as per the messages, you may need to enter the passwords
again , enter it.
answered Jun 14, 2017 at 9:46
2
I know this is an old question, but thought I would post my solution for others who come across this post.
- Login to your Netgear D6000 router
- Click on the Advanced tab
- Click on Setup from the left hand menu
- Click on WAN Setup
- Tick the check box to Disable Port Scan and DoS Protection
- Click on Apply
Glorfindel
4,0598 gold badges23 silver badges37 bronze badges
answered Jul 4, 2017 at 16:00
StevePSteveP
1263 bronze badges
In my case, I had some commands in my .bashrc file which printed some general information (e.g. gcc --version) to the console whenever I logged in. These kind of outputs confused the FileZilla. I suppressed the commands and FileZilla worked immediately.
answered Mar 11, 2019 at 4:49
I was having the same problem, but I solved it by using IP adress in the host field
answered Jul 20, 2020 at 12:30
2
I managed to solve this problem by setting up Port Mapping and Port Trigger on the Router Modem :
Port Mapping and Port Trigger
answered Mar 14, 2021 at 9:48
Yes, its bcos of NAT ALG on my Skyworth Router. I disabled it and it fixed the issue instantly.
It was enabled by default, I unchecked it. Now Filezilla is working perfect.
You guys might find some similar options, so this is working solution. Thanks to fwilhelmsson for the idea.
answered Mar 23, 2021 at 9:04
I had the same issue when changing to a new AX5400 Wi-Fi 6 Router. I setup the NAT port forwarding like I had with my previous router and made sure my FTP server nic had a static IP assigned that was the same as what I used in port forwarding settings (192.168.1.161) but it would not allow remote connections. I was finally able to get a successful connection when I went to «Advanced» tab, selected «network», and finally clicked on «Routing». From there I added a new route to my Static Routing table. I set the local IP of my FTP (192.168.1.161) server as the «Network Destination», Local network IP (255.255.255.0) as «Subnet Mask», my routers local IP (192.168.1.1) as «Default Gateway», set LAN as «Interface», and used FTP as my «Description». After adding this static routing I tested and was finally able to connect.
answered Dec 20, 2021 at 17:29
1
hi all,
trying to get vsftpd working with ftps ie active as passive is ftpes,
i am nearly getting there just getting stuck on the last hurdle
it connects via filezilla as it asks me to accept the self signed ssl cert which i do and it logs in but fails it gives me this —
———————————————————
Connecting to 192.168.100.15:990…
Status: Connection established, initializing TLS…
Status: Verifying certificate…
Status: TLS connection established, waiting for welcome message…
Status: Logged in
Status: Retrieving directory listing…
Command: PWD
Response: 257 «/»
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PASV
Response: 550 Permission denied.
Command: PORT 172,16,9,1,203,248
Response: 200 PORT command successful. Consider using PASV.
Command: LIST
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Connecting to 192.168.100.15:990…
Status: Connection established, initializing TLS…
Status: Verifying certificate…
Status: TLS connection established, waiting for welcome message…
Status: Logged in
Status: Retrieving directory listing…
Command: PWD
Response: 257 «/»
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PASV
Response: 550 Permission denied.
Command: PORT 172,16,9,1,203,250
Response: 200 PORT command successful. Consider using PASV.
Command: LIST
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
————————————————————————————————————
and this is my config file —
———————————————-
# Example config file /etc/vsftpd/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd’s
# capabilities.
#
# Allow anonymous FTP? (Beware — allowed by default if you comment this out).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd’s)
local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages — messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# The target log file can be vsftpd_log_file or xferlog_file.
# This depends on setting xferlog_std_format parameter
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using «root» for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# The name of log file when xferlog_enable=YES and xferlog_std_format=YES
# WARNING — changing this filename affects /etc/logrotate.d/vsftpd.log
#xferlog_file=/var/log/xferlog
#
# Switches between logging into vsftpd_log_file and xferlog_file files.
# NO writes to vsftpd_log_file, YES to xferlog_file
xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command «SIZE /big/file» in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd/banned_emails
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
chroot_local_user=YES
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd/chroot_list
#
# You may activate the «-R» option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as «ncftp» and «mirror» assume
# the presence of the «-R» option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# When «listen» directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
listen=YES
#
# This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES
pam_service_name=vsftpd
userlist_enable=YES
tcp_wrappers=YES
rsa_cert_file=/ssl_certs/vsftpd.pem
rsa_private_key_file=/ssl_certs/vsftpd.pem
ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES
ssl_tlsv1=YES
ssl_sslv2=NO
ssl_sslv3=NO
require_ssl_reuse=NO
ssl_ciphers=HIGH
pasv_enable=NO
pasv_min_port=49152
pasv_max_port=65534
implicit_ssl=YES
listen_port=990
———————————————
if anyone could help me out i would be very grateful,
sorry for the long post
many thanks,
rob