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.
The passive ports range is not configured, either in
/etc/proftpd.d/*.conf. Alternatively, passive ports are not open in the firewall.
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.
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
PassivePortsparameter). 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.