Home > Uncategorized > Filezilla Server gives error: Disconnected from server: ECONNABORTED – Connection aborted

Filezilla Server gives error: Disconnected from server: ECONNABORTED – Connection aborted

I’ve suddenly started experiencing problems with Filezilla server. At present, the server version is Filezilla 0.9.34b, and FTP Client is Filezilla 3.3.3, or Firefox 3.6.8, or IE 7.0.5730.13

For Filezilla as a client, I get the following error:

Command:    TYPE I
Response:    200 Type set to I
Command:    PASV
Error:    Disconnected from server: ECONNABORTED - Connection aborted
Error:    Failed to retrieve directory listing

In the Server logs, I get no indication

(000010) 01/08/2010 16:26:41 - sailing2010 (> TYPE A
(000010) 01/08/2010 16:26:41 - sailing2010 (> 200 Type set to A
(000010) 01/08/2010 16:26:41 - sailing2010 (> PASV
(000010) 01/08/2010 16:26:41 - sailing2010 (> 227 Entering Passive Mode (192,168,0,5,3,226)
(000010) 01/08/2010 16:26:41 - sailing2010 (> disconnected.

If I connect using an older account via SSL, then it works fine. If I force the client to ACTIVE mode, then it works fine. This all happens with the client both inside and outside my Home LAN, with the FTP server’s host firewall turned on and off. I’ve tried around 15 times with no successful connects. I have PASV mode configured manually to ports 991-995, with these opened on the router and OS firewalls; these have been working fine with the same config for many months.

Evidentally there’s some kind of issue with Filezilla server, unencrypted connections, and PASV mode, that is to do with the server, not any firewalls.

Categories: Uncategorized
  1. April 12, 2011 at 5:16 am

    I am having the same issue. It is driving me nuts. Let me know if you figure it out.

    • damo
      April 12, 2011 at 6:31 am

      I never did, and there’s not much out there. In the end I guessed it was some low-level TCP stack issue due to latency, low bandwidth, and other issues. I ended up switching to direct SFTP rather than tunneled FTP.

  2. May 9, 2012 at 4:45 pm

    You must enable port 443 on firewall to server

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: