- Plesk for Linux
- Plesk for Windows
It is not possible to connect to a Plesk server (or if connected, copy files) via FTP in the passive mode. One of the following error messages appears during connection (Error message varies depending on FTP client):
PLESK_INFO: 530 Login incorrect.
PLESK_INFO: ftp: connect: Connection refused
PLESK_INFO: Response: 227 Entering Passive Mode (203,0,113,111,250,241).
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
PLESK_INFO: ftp: connect: Connection timed out
PLESK_INFO: 425 Can't open data connection.
PLESK_INFO: An error occurred opening that folder on the FTP server. Make sure you have permission to access that folder. The operation timed out
PLESK_INFO: Error listing directory '/httpdocs'. Transfer channel can't be opened. Reason: No connection could be made because the target machine actively refused it. Could not retrieve directory listing
PLESK_INFO: Connecting data socket to (203.0.113.2) port 39383
Socket error (Connection timed out) - reconnecting
It is not possible to get a directory listing by FTP using Secured TLS: the connection establishes but directory listing does not work. The following errors appear in
CONFIG_TEXT: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: Permission denied
pam_systemd(proftpd:session): Failed to connect to system bus: Permission denied
pam_listfile(proftpd:auth): Couldn't open /etc/ftpusers
The passive port range (by default, 49152-65535) is not properly configured.
Configure the passive port range:
Plesk for Linux
Plesk for Windows Server
Plesk for cloud solutions
Open Access to Plesk Services on an Amazon Lightsail Instance
Configuring the Passive FTP Mode on a Microsoft Azure Instance
Installing Plesk on Alibaba Cloud (Opening Ports Used by Plesk section)
Please sign in to leave a comment.