Error: connect: Unexpected end event

[ankit2049]

This error is crashing the server. I am on version 11.0.0

connect() calls addTempListeners(this, 'connect') without a reject argument

Inside the connect method, we have this line:

listeners = addTempListeners(this, 'connect');

However, the 'getConnection' call does pass the reject, so if the SSH2 'end' event fires during getConnection, it correctly calls reject(newError), turning into a Promise rejection.

Is there any specific reason it is designed in such a way? Can we do something like this:

listeners = addTempListeners(this, 'connect', (err) => {
      throw this.fmtError(err, 'connect');
});

[theophilusx]

From memory, I think the reason there is no reject is that it broke the code which manages the connection retries. Having a reject resulted in no subsequent retries being attempted after a failure. To be honest, I have never liked the retry code. It was originally added via a PR and I wsas hesitant to add it at the time, but bowed down to pressure. It has resulted in far more complex connection code than I would prefer. One side effect is that you have the corner case your experiencing. I will try to find time in the next month to have a look and retest with using reject, but I'm not confident. A big problem is reproduction. Very hard to trigger thye connection error at just the right point to trigger what you are seeing. If you wanted to try some fixes, quite willing to consider PRs provided all tests in the test suite pass.

[MrNghia123]

I am having the exact problem.
Do you have any workaround @ankit2049 ?

[bboltze]

I think I might have the same issue when using the ssh hostVerifier options.
When the verifier returns false, connect() simply hangs. Using getConnection() followed by getSftpChannel() works as expected, i.e. the getConnection() Promise is rejected.