Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR: ERR_GENERIC_CLIENT - This service allows sftp connections only

See original GitHub issue

I don’t know what needs to be done here!!

sftp.connect({
  host: 'host',
  port: '22',
  username: 'username',
  password: 'pass',
  debug: myDebug,
})

I am getting the following error.

DEBUG: Parser: IN_PACKETDATAAFTER, packet: USERAUTH_FAILURE
DEBUG: Client: password auth failed
CLIENT[sftp]: Exhausted all connection attempts. Giving up
DEBUG: Outgoing: Writing DISCONNECT (BY_APPLICATION)
Error: connect: All configured authentication methods failed after 2 attempts
    at Object.formatError (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2-sftp-client/src/utils.js:62:18)
    at Client.connectErrorListener (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2-sftp-client/src/index.js:98:21)
    at Object.onceWrapper (events.js:422:26)
    at Client.emit (events.js:315:20)
    at doNextAuth (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2/lib/client.js:415:12)
    at tryNextAuth (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2/lib/client.js:484:5)
    at SSH2Stream.onUSERAUTH_FAILURE (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2/lib/client.js:597:5)
    at SSH2Stream.emit (events.js:315:20)
    at parsePacket (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2-streams/lib/ssh.js:3682:10)
    at SSH2Stream._transform (/Users/XXXX/dev/workspaces/proc-order-sync/node_modules/ssh2-streams/lib/ssh.js:701:13) {
  code: 'ERR_GENERIC_CLIENT',
  custom: true

It looks like authentication is failing, although I can successfully connect with the same information using CyberDuck a MAC OS app.

Issue Analytics

State:
Created 3 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

2reactions

kaaljabrcommented, May 4, 2020

I got it fixed by doing the following:

tryKeyboard: true

and

client.on('keyboard-interactive', (name, instructions, instructionsLang, prompts, finish) => {
  console.log('name %s, instructions %s, instructionsLang %s, prompts', name, instructions, instructionsLang, prompts);
  finish([config.password]);
});

0reactions

theophilusxcommented, May 6, 2020

Well, all I can say is I’ve never needed to do that and all the ftp servers I’ve communicated with work fine. It could be that the remote server is configured to only allow authentication from the keyboard (which would be unusual). It certainly isn’t a ‘normal’ setup, but if it works…

– Tim Cross