• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Can't connect via FTP with some clients

D4NY

Regular Pleskian
Hi everyone,
i've a strange situation on my Ovh Centos 6.8 Plesk 12.5 dedicated server. Suddenly (maybe after a freeze and phisical reboot) some users have problems connecting via FTP with clients like Filezilla of FileExplorer. They got a message like "A connection attempt failed because the connected party did not responded after a period of time". I've tried login with CuteFTP client and i log in after some seconds. If i try with Filezilla no way to login.

Before this issue with CuteFtp i login immediatly, exactly as on a second server with the same configuration. Log in is immediate and it works also with Filezilla and other clients.

What happened? Can someone help me?
Thank you
 
1) both clients are in passive mode. FileZilla not working (timeout). CuteFTP lasts lot of seconds and then log in and it's fast as normal.

2) no software firewall
 
There is a possibility that the connection is proxied or that a virus on your system or an antivirus-software is interfering with it.
 
Hi D4NY,

1) Could you provide detail logs from FileZilla?
2) Did you check OVH's firewall, client computer's firewall and server's firewall?
 
Same issue here. Filezilla is not working on both Windows and Mac. Transmit on Mac has no issues at all.

Below the detail logs from FileZilla

Code:
Status:      Resolving address of ftp.domain.com
Status:      Connecting to x.x.x.x:21...
Status:      Connection established, waiting for welcome message...
Status:      Initializing TLS...
Status:      Verifying certificate...
Status:      TLS connection established.
Status:      Logged in
Status:      Retrieving directory listing of "/httpdocs"...
Command:    CWD /httpdocs
Response: 250 CWD command successful
Command:    PWD
Response: 257 "/httpdocs" is the current directory
Command:    TYPE I
Response: 200 Type set to I
Command:    PASV
Response: 227 Entering Passive Mode (x,x,x,x,156,184).
Command:    MLSD
Error:        Connection timed out after 20 seconds of inactivity
Error:        Failed to retrieve directory listing
 
Response: 227 Entering Passive Mode (x,x,x,x,156,184).
In documentation, we recommend using 49152-65535 port range. Your FTP server asked FTP client use 40120/tcp port for passive connection but connection timed out.

Check what exactly port range do you use for passive FTP connection and allow it in firewalls (system's firewall; cloud's firewall if the system works in a cloud environment).

...or maybe some wrong with a firewall on a client side and the firewall blocks the outgoing connection.
Anyway, all this look like a network issue.
 
Back
Top