Can't parse response to 'EPSV': 227 Entering Passive Mode (91,190,231,97,119,66).

[thomaschaaf]

Describe the bug
This is only happening with some ftp servers.

Example code

const ftp = require("basic-ftp")

example()

async function example() {
    const client = new ftp.Client()
    client.ftp.verbose = true
    try {
        await client.access({
            host: "###",
            user: "###",
            password: "###",
            secure: false
        })
        console.log(await client.list())
    }
    catch(err) {
        console.log(err)
    }
    client.close()
}

Console output

Connected to ###.###.###.###:21 (No encryption)
< 220 Wilkommen auf dem FTP Server der ###.

Login security: No encryption
> USER ###
< 331 Password required for ###

> PASS ###
< 230 Logged on

> TYPE I
< 200 Type set to I

> STRU F
< 200 Using file structure 'File'

> OPTS UTF8 ON
< 202 UTF8 mode is always enabled. No need to send this command.

> OPTS MLST type;size;modify;unique;unix.mode;unix.owner;unix.group;unix.ownername;unix.groupname;
< 200 MLST OPTS type;size;modify;

Trying to find optimal transfer strategy...
> EPSV
< 227 Entering Passive Mode (91,190,231,97,119,66).

Error: Can't parse response to 'EPSV': 227 Entering Passive Mode (91,190,231,97,119,66).

Which version of Node.js are you using?
v14.6.0

[mofux]

Looks like the server is responding with the wrong status code. It should respond with 229 status code to the EPSV request. The 227 response code is for the PASV command... 🤔 On what kind of FTP server is this happing?

[thomaschaaf]

I don't know as I am just using it. It's ftp.blue-technologies.de is there a way to find out without asking them?

[patrickjuchli]

Interesting, the message itself also contains instructions for PASV, not EPSV. I believe that's an error, it should respond with an error code 5xx. This library would then try PASV.

You can force the client to only use PASV like so:

const ftp = require("basic-ftp")
client.prepareTransfer = ftp.enterPassiveModeIPv4

[patrickjuchli]

By the way, this seems to be a duplicate: #135.

[patrickjuchli]

A new version 4.6.3 might handle this case, let me know if it works.