For the past few days I have been having difficulty connecting to FTP

[persoblog]

Hello
For the past few days I have been having difficulty connecting to FTP to my hosting, indeed an error message appears, except if I use winscp the access is successful without worries here are the error messages

Status: Address resolution of ftp.cercleduzero.org
Status: Connecting at 185.41.152.40:21...
Status: Connected, waiting for greeting...
Status: Initializing TLS...
Status: TLS connection established.
Status: The server does not support non-ASCII characters.
Status: Connected
Status: Retrieving folder contents...
Command: PWD
Answer: 257 "/" is the current directory
Command: TYPE I
Answer: 200 Type set to I
Command: PASV
Answer: 227 Entering Passive Mode (185,41,152,40,215,108).
Command: MLSD
Error: Connection aborted after 20 seconds of inactivity
Error: Unable to retrieve folder contents
Status: Disconnected from server
Status: Address resolution of ftp.cercleduzero.org
Status: Connecting at 185.41.152.40:21...
Status: Connected, waiting for greeting...
Status: Initializing TLS...
Status: TLS connection established.
Status: The server does not support non-ASCII characters.
Status: Connected
Status: Retrieving folder contents...

note that even if it indicates recovery of the contents of the file it returns in error then

[botg]

Most likely there is a firewall or NAT router interfering with the data connection. You can use https://ftptest.net/ to figure out whether it's on the server's end or on your end or the connection.

[persoblog]

Here is the result emitted from https://ftptest.net/


Status: Resolving address of ftp.cercleduzero.org

Status: Connecting to 185.41.152.40

Warning: The entered address does not resolve to an IPv6 address.

Status: Connected, waiting for welcome message...

Reply: 220 ProFTPD Server (ProFTPD Default Installation) [::ffff:185.41.152.40]

Command: CLNT https://ftptest.net on behalf of 80.218.88.208

Reply: 200 OK

Command: AUTH TLS

Reply: 234 AUTH TLS successful

Status: Performing TLS handshake...

Status: TLS handshake successful, verifying certificate...

Status: Received 1 certificates from server.

Status: cert[0]: subject='CN=infrastructure.cgweb-creator.fr' issuer='C=US,ST=TX,L=Houston,O=cPanel\5c, Inc.,CN=cPanel\5c, Inc. Certification Authority'

Command: USER circleduzero

Reply: 331 Password required for cercleduzero

Command: PASS *************

Reply: 230 User cercleduzero logged in

Command: SYST

Reply: 215 UNIX Type: L8

Command: FEAT

Reply: 211-Features:

Reply: AUTH TLS

Reply: CCC

Reply: CLNT

Reply: EPRT

Reply: EPSV

Reply: HOST

Reply: MDTM

Reply: MFF modify;UNIX.group;UNIX.mode;

Reply: MFMT

Reply: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;

Reply: PBSZ

Reply: PROT

Reply: REST STREAM

Reply: SIZE

Reply: SSCN

Reply: TVFS

Reply: 211 End

Command: PBSZ 0

Reply: 200 PBSZ 0 successful

Command: PROT P

Reply: 200 Protection set to Private

Command: PWD

Reply: 257 "/" is the current directory

Status: Current path is /

Command: TYPE I

Reply: 200 Type set to I

Command: PASV

Reply: 227 Entering Passive Mode (185,41,152,40,250,229).

Command: MLSD

Error: Connection timed out



I want to specify that exactly the same procedure is done on winscp and that it works.

It seems to come directly from Filezilla

[botg]

Last time I checked WinSCP is insecure, it does not use FTP over TLS by default.

If your server fails the test on ftptest.net, it is a server-side issue. Only the server administrator or server hosting provider can fix it.