Article ID: 119525, created on Jan 8, 2014, last review on Sep 14, 2016

  • Applies to:
  • Plesk Automation

Symptoms

It is not possible to connect to FTP in passive mode Plesk Automation Service node. One of the following errors occurs when connecting via FTP:

227 Entering Passive Mode  
ftp: connect: Connection refused


Response:       227 Entering Passive Mode (1,2,3,4,5,17).
Error:  Connection timed out
Error:  Failed to retrieve directory listing

Response:       227 Entering Passive Mode (1,2,3,4,5,17).
ftp: connect: Connection timed out


Response:       227 Entering Passive Mode (111,235,75,26,192,30).
Command:        LIST
Response:       425 Can't open data connection.
Error:  Failed to retrieve directory listing.

Cause

The passive ports range is not configured, either in /etc/proftpd.conf or /etc/proftpd.d/*.conf. Alternatively, passive ports are not open in the firewall.

Resolution

  1. If you are using NAT, make sure it is configured correctly. You need to configure the ProFTPD service properly by adding the PassivePorts and MasqueradeAddress parameters. If you are using Amazon services, please contact Amazon AWS support to resolve the issue.

  2. Make sure the passive ports range has been configured in the additional configuration ('.conf') file inside the '/etc/proftpd.d/' directory (check the content of files '50-plesk.conf' or '60-ppa.conf' if they exist and find the PassivePorts parameter). If not, create the configuration file manually. For example 'passive_ports.conf':

    cat /etc/proftpd.d/passive_ports.conf |grep -ir passive
    PassivePorts 30000 30400
    

The port range selected must be in the non-privileged range (e.g., greater than or equal to 1024); it is STRONGLY RECOMMENDED the chosen range be large enough to handle many simultaneous passive connections (for example, 49152-65534, the IANA-registered ephemeral port range).

    # Use the IANA registered ephemeral port range
    PassivePorts 49152 65534

The ports range also should be allowed for incoming connections in your firewall.

For additional instruction on configuring Passive FTP port range on a Windows Server, please refer to How to configure Passive FTP port range on Windows Server.

Search Words

unable to login to ftp

cant access ftp

ftp passive

Could not retrieve directory listing Error listing directory '/'.

FTP connection refused EC2

ftp connextion tls

ftp doesnt work correctly

CLOSE_WAIT

proftp issue after upgrade

unable to access ftp

ftp is not connecting

proftpd not start

Failed to retrieve directory listing

FTP IssuesFailed to retrieve directory listing

Unable to FTP to website Passive mode is refused.

ftp error

не подключается по ftp

ftps directory listing

FTP Problems

filezilla

ftp not working on server

ftp

Connect via FTP hangs at "MLSD"

Error FTP transfer

ftp The network connection was aborted by the local system.

FTP TLS Problem

FTP not working

Timeout detected. (data connection) Could not retrieve directory listing

we can log into the ftp but can not see folders on /httpdocs

ftp list timeout

firewall centos

ftp will not display directory listings

ftp tls

ftp: connect: Connection refused

Can not connect to FTP in passive mode

FTp Filezilla TLS

Server sent passive reply with unroutable address. Using server address instead.

FTP Access

ftp connection timeout

500 critical file transfer error

Unable to connect using FTP

FTP

Превышено время ожидания соединения

Unable to get directory listing for FTP

Unable to retrieve directory listing in FTP

Critical error: Could not connect to server

ftps

Unable to get directory listing when connecting using FTP

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF