105

I'm running Filezilla Server 0.9.45 beta to manage my server remotely. After setting it up, I tested connecting to it using the IP 127.0.0.1, and it worked successfully. However, to connect to the server remotely, I port forwarded to port 21, and tried to connect using my computer's IP.

Status: Connecting to [My IP]:21...
Status: Connection established, waiting for welcome message...
Response:   220 Powered By FileZilla Server version 0.9.45 beta
Command:    USER hussain khalil
Response:   331 Password required for user
Command:    PASS *********
Response:   230 Logged on
Status: Connected
Status: Retrieving directory listing...
Command:    CWD /
Response:   250 CWD successful. "/" is current directory.
Command:    PWD
Response:   257 "/" is current directory.
Command:    TYPE I
Response:   200 Type set to I
Command:    PORT 192,168,0,13,205,63
Response:   200 Port command successful
Command:    MLSD
Response:   150 Opening data channel for directory listing of "/"
Response:   425 Can't open data connection for transfer of "/"
Error:  Failed to retrieve directory listing

This continues to work locally, but not when connecting remotely... How can I fix this?

Hussain Khalil
  • 1,520
  • 2
  • 15
  • 24
  • Hay All, How about in prestashop? I've tried the Cary's answer with sftp.pswebstore.com, but status says Connection attempt failed with "ECONNREFUSED - Connection refused by server" – Peternak Kode Channel Jun 25 '16 at 02:03

26 Answers26

153

I just changed the encryption from "Use explicit FTP over TLS if available" to "Only use plain FTP" (insecure) at site manager and it works!

Vangelis Kotrotsios
  • 1,719
  • 3
  • 11
  • 3
  • 42
    If you want security this is a bad idea. – DarrellNorton Feb 04 '15 at 14:59
  • 2
    @DarrellNorton So what's the way to ensure security as well as retrieving the directory listing? – Faizan Apr 09 '15 at 19:37
  • @Faizan you have to use FTPS. This answer says to disable security. Vaggelis clear states this is insecure. The most likely reason the PASV command is failing is that the FTP Server is sending a response but the firewall is not allowing outbound communication on those ports. See San Bergam's answer in the accepted response. – DarrellNorton Apr 10 '15 at 14:02
  • 3
    @Faizan the detailed technical explanation is here: https://wiki.filezilla-project.org/Network_Configuration - I had to look at that a bit before I understood the difference between active and passive, and explicit versus implicit FTPS. My issue ended up being the firewall was blocking the implicit FTPS port range, which I set to 50,000 - 55,000. Once the network admin explicitly allowed outbound on those ports, it worked perfectly. – DarrellNorton Apr 10 '15 at 14:09
  • 1
    Take note that this will really disable your security, yes it will worked but in can leave a problem sooner or later! – Cary Bondoc Aug 05 '15 at 07:09
  • Don't throw security to trash. – Pedro Adame Vergara May 08 '17 at 10:21
  • Its works for me also. Maybe this is related to SSL, right? –  Jan 16 '19 at 06:16
  • I am using IIS ftp how can i do this ? – Moeez Oct 15 '21 at 05:30
92

File > Site Manager > Select your site > Transfer Settings > Active

Works for me.

Marcos Nakamine
  • 1,286
  • 17
  • 29
40

Most of the answers here involves configuring, actually just by adding sftp:// on your host (see below image) you can instantly fixed that kind of problem, works for me.

enter image description here

And also take note that if you follow Vaggelis guide you are lowering your security, sftp is better than using plain ftp.

I just changed the encryption from "Use explicit FTP over TLS if available" to "Only use plain FTP" (insecure) at site manager and it works!

Community
  • 1
  • 1
Cary Bondoc
  • 2,923
  • 4
  • 37
  • 60
37

When you send the port command to your server, you are asking the server to connect to you (on the remote network). If the remote network also has a NAT router, and you have not port-forwarded the port you are sending with your PORT command, the server will not be able reach you.

The most common solution would be to send the PASV command to the server instead of the PORT command. The PASV command will ask the server to create a listening socket and accept a connection from the remote machine to establish the data connection.

For the PASV command to work, you will also need to port-forward a range of ports for the passive data connections. The passive connection ports (which need to be forwarded) should be listed in the FileZilla documentation.

Evan
  • 572
  • 4
  • 5
20

Ok this helped a lot, I couldn't find a fix.

Simply, I already port forwarded the FTP port to my server. (The default is 14147, I'll use this as example)

Go to Edit > General settings, Listening port should be the one your using, in this case 14147.

Then go to Passive Mode Settings, I checked "Use Custom Port", and entered in the Range 50000 - 50100.

Then on your router, port forward 50000 - 50100 to the server IP locally.

IPv4 specific settings I left at default, reconnected my client, and bam now the file listing appears.

Ensure your servers firewall has an inbound rule set to accept 14147, and 50000-50100.

Basically what Evan stated. I can't attest to the security of opening these ports, but this is what finally got my Filezilla client and server to communicate and view files. Hope this helps someone.

Home Nerd
  • 209
  • 3
  • 3
  • 1
    "Ensure your servers firewall has an inbound rule set to accept 14147, and 50000-50100" -> this comment save my days – Rocky Andra Mar 04 '16 at 06:48
  • I have just installed FileZille Server at work and I can get through my folder with FileZille Cliet. Th issue is when I am trying to connect via PHP using nicolab's library. I keep on getting "Unable to connect" exception. Any ideas? I know this may have everything to do with our company's firewall. Thanks in advance. – scruffycoder86 May 20 '16 at 12:11
  • 1
    Thats the key "Ensure your servers firewall has an inbound rule set to accept 14147, and 50000-50100." Thanks mate, upvoted! – Hitin Feb 06 '17 at 17:53
  • Found that my ports (40110-40310) were closed i thought 21 was enough – Sodj May 23 '21 at 14:55
  • this solition solved my problem. – cancan Jul 25 '22 at 14:18
  • Worked for me. I had to allow that range of ports in Windows Firewall – Daniel Williams Sep 12 '22 at 17:00
10

My experience is that the new version of Filezilla has this problem, but not the old versions. I was using Filezilla and everything was OK. After I upgraded to version 3.10, I faced this problem and I couldn't solve it. I uninstalled version 3.10 and reinstalled version 3.8 and the problem was gone! Now I am using version 3.8 and everything is OK. I prefer to face no problems even if I have to use old versions. ;)

Try installing the old version and do not upgrade, however odd that may sound.

Dennis Meng
  • 5,109
  • 14
  • 33
  • 36
  • i just downloaded 3.8 version from [here](https://community.akamai.com/blogs/dwichandra/2015/01/16/obtaining-old-version-of-filezilla), with Encryption: 'Plain Ftp' and Transfer settings: 'Passive' – Shaiju T Jan 03 '16 at 12:44
  • I have a weird situation where I can access various sites using FileZilla client (3.22) using TLS, But one site I can only access using plain FTP. This has happened sometime in the last few months (since the last time I went to this site) because it used to work fine with TLS. – Marc Wilson Dec 08 '16 at 23:08
10

I solved this by going into Site Manager -> selected the connection that Failed to retrieve directory listing -> Switched to tab "Transfer Settings" and set "Transfer Mode" to "Active" instead of "Default". Also check if you are connected via VPN or anything similar, this can also interfere.

Ogglas
  • 62,132
  • 37
  • 328
  • 418
8

Run Windows Defender Firewall with Advanced Security

Start > Run : wf.msc

enter image description here

Alper Ebicoglu
  • 8,884
  • 1
  • 49
  • 55
3

I had the same problem-what worked for me -in Windows OS-is adding FileZilla as a firewall exception-under allow a program through firewall features

IjonTichy
  • 96
  • 1
  • 1
  • 10
3

I've had the same problem, This was due to the firewall. I use windows server,

Can you allow the connection permission for program, intead of port 21,22 permission.

Windows Firewall with Advanced Security->
Inbound Rules->
Add Rule->
Program->
"Select Filezilla path with Browse button"->
Allow the Connection
Ferhat KOÇER
  • 3,890
  • 1
  • 26
  • 26
2

I had Filezilla 3.6, and had the same issue as OP. I have upgraded to 3.10.3 thinking it would fix it. Nope, still the same.

Then I did a bit digging around the options, and what worked for me is:

Edit -> Settings -> FTP -> Passive Mode and switched from "Fall back to active mode" to "Use the server's external IP address instead"

Zoran P.
  • 870
  • 1
  • 13
  • 16
2

After about 2 hours experience;

  • Open > Windows Defender Firewall with Advanced Security
  • Select > Inbound Rules
  • Click > New Rule...
  • Choose > Custom
  • Choose > This program path:
  • Click > Browse
  • Find > filezilla-server.exe (possibly C:\Program Files\FileZilla Server)
  • Click > Open
  • Click > Next
  • Click > Next
  • Click > Next (Allow the connection is already selected)
  • Click > Next (if you do not need change)
  • Fill > Name
  • Click > Finish
Furkan Ekinci
  • 2,472
  • 3
  • 29
  • 39
1

I experienced the same problem with FZ-client, while my notebook connected via WLAN and DSL/Router. In the Site Manager connection settings I was applied Host:ftp.domain-name, Encryption:Only use plain FTP (insecure) and User:username@domain-name. Then the FTP-client succesfully connected to my website server. More FTP connection information could be found in the CPanel of the webserver. Hope this helps.

Pram
  • 11
  • 3
1

I had that problem with my server hosted in the cloud. I only need the server a couple of times a year and so when I boot up my server the IP address changes. The new IP address then has to be updated on FTP Server passive mode settings!

The latest version of Filezilla works just fine!

chhenning
  • 2,017
  • 3
  • 26
  • 44
  • Similar experience here. I have a static IP, and I'm sitting behind a router. That static IP changed, and I had to update my passive mode settings to reflect the new IP. – Mmm Jun 07 '23 at 19:04
1

It worked for me:

General -> Encryption -> Only use plain FTP

Transfer settings -> Transfer Mode -> Active

Consider that it is very insecure, and must be used only for testing.

joaq.dlt
  • 21
  • 1
0

I also had the problem after upgrading to 3.10. I had versoin 3.6.02 hanging around and installed that. Problem solved.

0

If you're using VestaCP, you might want to allow ports 12000-12100 TCP on your Linux Firewall.

You can do this in VestaCP settings.

Lucas Bustamante
  • 15,821
  • 7
  • 92
  • 86
0

Check if the ip address on the router is the same with the one on the ftp server. If not make sure it is the same. This should works perfectly.

favourworks
  • 131
  • 3
0

In my case, restarting my router which I used to connect to the internet worked. I think too much of connections were going from the same IP Address and when I restarted my router, possibly a new IP was assigned and now everything works fine, and passive mode gives good speed in directory listing.

Reejesh PK
  • 658
  • 1
  • 11
  • 27
0

My issue was also the firewall. I'm using a Linux server with WHM/cPanel. Adding my IP to the quick allow solved my issue. I hadn't updated Filezilla and I don't think there were any changes to the server that should have caused it. However, I did move and my IP changed so maybe that was the problem. Good luck to everyone else with this insanely annoying issue.

how to access WHM firewall config

0

The issue of mine was the same but the solution was a little different.

I used the AWS EC2 server to host the WHM service. And found that "the passive ports are enabled, but not these Ports are not found in my EC2 Security Group".

[root@94367392 ~]cPs# egrep -i passiveport /etc/pure-ftpd.conf

Output:

PassivePortRange 49152 65534

Now I moved ahead and opened the ports from 49152 to 65534 in the Security group of EC2 and the Filezilla problem related to "Failed to retrieve directory listing" was solved and it worked like a charm.

This cPanel doc is helpful.

Yun
  • 3,056
  • 6
  • 9
  • 28
0

I've seen solutions that involve granting FileZilla full access via windows firewall. This is an alternative to that, if you know the IP of the connecting system and it's static, simply grant it full access to all ports via windows firewall.

Windows Firewall, Inbound Rules > Create a Rule > All Local Ports > Scope > This IP Address (the IP of the connecting system).

To me this is much safer than granting full access to FileZilla to all incoming ip addresses.

Once you've completed your transfer, you can then disable the rule.

J. Minjire
  • 1,003
  • 11
  • 22
0

I tried all the solution, i used CyberDuck and it works..

Alessandro
  • 305
  • 2
  • 8
  • 22
0

I have disable IPv6 on my local Mac from System Preference->Network->{YourConnection}->Advanced->IPv6, I have selected Manually for IPv6.

After changing it back to Automatically fix the FileZilla issue.

0

Filezilla's error messages are not always showing giving the entire picture. Note that this very same error message may be caused by server side misconfiguration.

One client has recently changed their IP and faced the the same issue. Switching to active mode did not work and using TLS was mandatory.

At the end we had to create a firewall rule to allow the passive port range "10090-10100" for the specific client's IP in consideration.

After that the client was able to connect normally via passive mode and retrieve the directory listing.

So if you face this issue and everything else has failed, do check the firewall passive ports at server side.

Majte
  • 264
  • 2
  • 9
-1

Now in FileZilla, create a new Account 1. Host is the FTP Address - e.g. ftp.somewhere.com 2. Protocol is "SFTP-SSH File Transfer Protocol" 3. User ID is your Bluehost User Id 4. Password is your Bluehost Password 5. Click "Connect" to establish a connection with Directory Listing!

This resolve the issue with 3.10 for me. And I'm glad to have the Secure Access for all of my future file transfers. It should prevent security issues in the future.

Ramy Hassan
  • 47
  • 1
  • 3