TSL | LIST command returns No connection established

[DenisLevkovets]

Node version: 12.22.12
ftp-srv version: 4.6.2
FTP client: CyberDuck

Hi everyone!
I went throw a lot of opened and closed issues, but cannot solve one problem. The explicit ftp connection doesn't work either local or docker environment. The ftp server config is followed:

const FtpServer = new FtpSrv({
url: ftp://0.0.0.0:21,
pasv_url: 0.0.0.0,
pasv_min: 65500,
pasv_max: 65505,
anonymous: false,
tls: {
key: fs.readFileSync(${__dirname}/certs/server-key.pem),
cert: fs.readFileSync(${__dirname}/certs/server-cert.pem),
ca: [fs.readFileSync(${__dirname}/certs/ca-cert.pem)],
passphrase: 'qwerty'
},
});

It works on FTP protocol, but fails on FTPs.
Error: {"name":"ftp-srv","hostname":"...","pid":83295,"id":"f79f8302-ea3a-4c49-a5b3-a1ca2a13d087","ip":"127.0.0.1","directive":"LIST","level":50,"err":{"message":"operation timed out","name":"TimeoutError","stack":...}}

I started to add console.log statements in code of ftp-srv package and found out that connectionHandler was not called during tls.createServer method. It's common issue to #192 which was no solved.

@trs @matt-forster Any thoughts?

[DenisLevkovets]

@trs, @matt-forster Additional info. When it comes to execute LIST command I print the connection data and receive followed:

connector: Passive {
connection: FtpConnection {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
server: [FtpServer],
id: 'ce16e4fb-9cbf-4ed9-a4eb-04cbdf29de11',
commandSocket: [TLSSocket],
log: [Logger],
commands: [FtpCommands],
transferType: 'ascii',
encoding: 'utf8',
bufferSize: 0,
_restByteCount: 0,
_secure: true,
connector: [Circular],
username: 'hotel',
authenticated: true,
fs: [FileSystem],
[Symbol(kCapture)]: false
},
dataSocket: null,
....
}
}

Data socket in this case is null, but in simple FTP connection it equals to a normal Socket Object

[matt-forster]

Weird - I am seeing a passive connection object here, and you mentioned you were using explicit?

[DenisLevkovets]

Yes, as you see the url in server options starts from ftp://

This is explicit connection, right?

[DenisLevkovets]

Also, I tried to use resolve function from documentation for pasv_url and public-ip package, but it didn't help. The variants with '0.0.0.0', '127.0.0.1' and my own public ip didn't help too. As I understood, connectionHandler should be triggered on 'secureConnection' event, but something prevent this event.

[DenisLevkovets]

@matt-forster It's more weird, because my configuration is common to other configurations mentioned in closed issues when such problem was solved. Moreover, I clone this repository, launch the start.js file in test directory and get the same error

[matt-forster]

It might be a filesystem or permissions issue, the list command is not resolving any value, and the promise is not completing.

[DenisLevkovets]

It's repeated localy, on VM and inside docker. Few times I was passed throw login and get the list of files(somehow), but upload and download operations were failed

[DenisLevkovets]

FileZilla connected to my server with explicit TLS connection:)) CyberDuck and Commander One fails.