Open pmiddlet72 opened 6 years ago
Remote-FTP check valid features list. For multiple servers, it was a bad thing to have returned the feature list and included it. But he did not endorse it. That's why it checks. That is why the PASV is 2x.
Try 21 port? https://github.com/mscdex/node-ftp/issues/153#issuecomment-300454955
I have been over each one of the posts and this still seems to be an open bug. Any fixes for this?
Is there any fixes for this?
Similar to another issues on implicit FTPS over TLS: #153
Connection seems successful, but that's as far as I get (connection under similar conditions works in filezilla). I'm finding the following error after a successful connection:
(Remote FTP: Error: Unable to make data connection. Error: connect ECONNREFUSED 127.0.0.1:50392)
Here's the initial log of events from the console upon connection:
I get the additional notification of the data connection error, which doesn't show up in the console (why not?)
In bizarre fashion, if I do nothing, the following will occur:
Of course ends in
Error: Unable to make data connection. Error: connect ECONNREFUSED 127.0.0.1:50392
again.Overall, It's as if there's a connection, but a connection refusal error occurs when attempting to view the remote root folder. I can't tell if the problem is on the connection side or further remote requests issued to the server.
It doesn't seem the connection is being closed until it completely times out. I'm afraid if I decreased any of the connection or keepalive parameters in .ftpconfig (below), that it would try to reconnect ad nauseum until I killed Atom (or the american stat association site killed me 😏 ).
Here's my .ftpconfig:
Why are 2 EPSV events followed by ABOR being issued. Something I need to check in node-ftp ?