ECONNRESET Error using ftp
See original GitHub issueHello,
I am experiencing an issue on one windows machine trying to use node-ftp. The issue appears to be network related, as I can complete this on another machine without issue.
The script I am using is the following:
var FTP = require( 'ftp' );
var client = new FTP();
client.on( 'ready', onReady );
function onReady() {
client.list( '/', onList );
}
function onList( err, list ) {
if ( err ) console.log( err.stack );
else console.log( list );
}
client.connect( {
user: '',
password: '',
host: '',
debug: console.log.bind( console )
} );
The error is shown here:
FileZilla on the same machine with the same setup seems to work without issue.
Is there anything that could be causing this?
Thanks
Issue Analytics
- State:
- Created 8 years ago
- Reactions:6
- Comments:15
Top Results From Across the Web
FTP Upload Error: read ECONNRESET
I'm trying to upload certain artifacts to an ftp server in a release pipeline. I'm using the OOTB "File Upload task" and the...
Read more >How do I catch an ECONNRESET error using the basic FTP ...
I want my program to continue running after catching ECONNRESET. How do I do that? I'm using basic-ftp for my ftp library. Here's...
Read more >FTP uploading Error: read ECONNRESET - Mobirise Forums
Hi, I am trying to use the built-in FTP client but I am facing some issues. While exporting the first html page (index)...
Read more >ECONNRESET - Connection reset by peer - FileZilla Forums
Same experience: FileZilla 3 gives that error, FileZIlla 2 does not. My FTP host is Comcast. In FZ3, if I specify the subfolder...
Read more >Problem connecting to ftp server - Linux Forum
With Filezilla i get this error: Text. Could not read from transfer socket: ECONNRESET - Connection reset by peer.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems this happening when node code behind certain firewall, such as dell’s sonicwall. Set socket keep alive to false should fix this problem.
connection.js line 106
socket.setKeepAlive(false);
Add an option would be nice.
I was having the same problem, but after this command every all its okay now :
npm install @ionic/app-scripts@nightly --save-dev