node.js - ssh2 timed out while waiting for handshake -


i trying use node.js issue command line in linux servers via ssh. found https://github.com/mscdex/ssh2 , tried test out. here code , ready event never fired:

 var client = require('ssh2').client;   console.log('start ssh2...');  var conn = new client();  conn.on('ready', function() {     console.log('client :: ready');             conn.shell(function(err, stream) {               if (err) throw err;               stream.on('close', function() {                 console.log('stream :: close');                 conn.end();               }).on('data', function(data) {                 console.log('stdout: ' + data);               }).stderr.on('data', function(data) {                 console.log('stderr: ' + data);               });               stream.end('ls -l\nexit\n');             });  }).connect({    host: '12.12.12.12',    port: 22,    trykeyboard: true,    debug: console.log,    readytimeout: 99999,    username: 'root',    password: 'password'  });

i did set long readytimeout , trykeyboard true.

here log:

debug: local ident: 'ssh-2.0-ssh2js0.0.14' debug: client: trying 123.123.123.123 on port 22 ... debug: client: connected debug: parser: in_init debug: parser: in_greeting debug: parser: in_header debug: remote ident: 'ssh-2.0-openssh_6.2' debug: outgoing: writing kexinit debug: parser: in_packetbefore (expecting 8) debug: parser: in_packet debug: parser: pktlen:1540,padlen:7,remainlen:1536 debug: parser: in_packetdata debug: parser: in_packetdataafter, packet: kexinit debug: comparing kexinits ... debug: (local) kex algorithms: diffie-hellman-group-exchange-sha256,diffie-hellm an-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug: (remote) kex algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2- nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1 ,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug: kex algorithm: diffie-hellman-group-exchange-sha256 debug: (local) host key formats: ssh-rsa,ssh-dss debug: (remote) host key formats: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256 debug: host key format: ssh-rsa debug: (local) client->server ciphers: aes256-ctr,aes192-ctr,aes128-ctr,aes128-g cm,aes128-gcm@openssh.com,aes256-gcm,aes256-gcm@openssh.com,aes256-cbc,aes192-cb c,aes128-cbc,blowfish-cbc,3des-cbc,arcfour256,arcfour128,cast128-cbc,arcfour debug: (remote) client->server ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour 256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc ,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu .se debug: client->server cipher: aes256-ctr debug: (local) server->client ciphers: aes256-ctr,aes192-ctr,aes128-ctr,aes128-g cm,aes128-gcm@openssh.com,aes256-gcm,aes256-gcm@openssh.com,aes256-cbc,aes192-cb c,aes128-cbc,blowfish-cbc,3des-cbc,arcfour256,arcfour128,cast128-cbc,arcfour debug: (remote) server->client ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour 256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc ,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu .se debug: server->client cipher: aes256-ctr debug: (local) client->server hmac algorithms: hmac-md5,hmac-sha1,hmac-sha2-256, hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-sha1-96,hmac -md5-96 debug: (remote) client->server hmac algorithms: hmac-md5-etm@openssh.com,hmac-sh a1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-25 6-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,h mac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac- 64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,h mac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug: client->server hmac algorithm: hmac-md5 debug: (local) server->client hmac algorithms: hmac-md5,hmac-sha1,hmac-sha2-256, hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-sha1-96,hmac -md5-96 debug: (remote) server->client hmac algorithms: hmac-md5-etm@openssh.com,hmac-sh a1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-25 6-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,h mac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac- 64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,h mac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug: server->client hmac algorithm: hmac-md5 debug: (local) client->server compression algorithms: none debug: (remote) client->server compression algorithms: none,zlib@openssh.com debug: client->server compression algorithm: none debug: (local) server->client compression algorithms: none debug: (remote) server->client compression algorithms: none,zlib@openssh.com debug: server->client compression algorithm: none debug: outgoing: writing kexdh_gex_request debug: parser: in_packetbefore (expecting 8) debug: parser: in_packet debug: parser: pktlen:404,padlen:8,remainlen:400 debug: parser: in_packetdata debug: parser: in_packetdataafter, packet: kexdh_gex_group debug: outgoing: writing kexdh_gex_init debug: parser: in_packetbefore (expecting 8) debug: parser: in_packet debug: parser: pktlen:956,padlen:7,remainlen:952 debug: parser: in_packetdata debug: parser: in_packetdataafter, packet: kexdh_gex_reply debug: checking host key format debug: checking signature format debug: verifying host fingerprint debug: host accepted default (no verification) debug: verifying signature debug: outgoing: writing newkeys debug: parser: in_packetbefore (expecting 8) debug: parser: in_packet debug: parser: pktlen:12,padlen:10,remainlen:8 debug: parser: in_packetdata debug: parser: in_packetdataafter, packet: newkeys debug: outgoing: writing service_request (ssh-userauth) debug: parser: in_packetbefore (expecting 16) debug: parser: in_packet debug: parser: decrypting debug: parser: pktlen:28,padlen:10,remainlen:16 debug: parser: in_packetdata debug: parser: decrypting debug: parser: hmac size:16 debug: parser: in_packetdataverify debug: parser: verifying mac debug: parser: in_packetdataverify (valid hmac) debug: parser: in_packetdataafter, packet: service_accept debug: outgoing: writing userauth_request (password) debug: parser: in_packetbefore (expecting 16) debug: parser: in_packet debug: parser: decrypting debug: parser: pktlen:44,padlen:7,remainlen:32 debug: parser: in_packetdata debug: parser: decrypting debug: parser: hmac size:16 debug: parser: in_packetdataverify debug: parser: verifying mac debug: parser: in_packetdataverify (valid hmac) debug: parser: in_packetdataafter, packet: userauth_failure debug: client: password auth failed debug: outgoing: writing userauth_request (keyboard-interactive) debug: parser: in_packetbefore (expecting 16) debug: parser: in_packet debug: parser: decrypting debug: parser: pktlen:44,padlen:11,remainlen:32 debug: parser: in_packetdata debug: parser: decrypting debug: parser: hmac size:16 debug: parser: in_packetdataverify debug: parser: verifying mac debug: parser: in_packetdataverify (valid hmac) debug: parser: in_packetdataafter, packet: userauth_info_request debug: parser: in_packetbefore (expecting 16) events.js:85       throw er; // unhandled 'error' event             ^ error: timed out while waiting handshake     @ null._ontimeout (\node_modules\ssh2\lib\client.js:138:17)     @ timer.listontimeout (timers.js:110:15)

however, if change ssh server configuration have private key in node.js server, authenticate. question why username/password authentication doesn't work , how fix (either code or change server configs somehow)?


Comments

Post a Comment

Popular posts from this blog

symfony - TEST environment only: The database schema is not in sync with the current mapping file -

there similar questions regarding issue haven't seen in particular test environment , sqlite. cannot validate schema test environment uses sqlite can validate schemas dev environment uses mysql. know reason , possible solution? whole application works fine in both dev , test environments though. phing , ci build broken. php app/console doctrine:schema:update --force --env=test updating database schema... database schema updated successfully! "9" queries executed php app/console doctrine:schema:validate --env=test [mapping] ok - mapping files correct. [database] fail - database schema not in sync current mapping file. update i'm adding sqldump result see if spots wrong it. thing can is, have 2 bundles. country below coming frontendbundle user entity missing defined in backendbundle . php app/console doctrine:schema:update --dump-sql --env=test drop index uniq_5373c9665e237e06; drop index uniq_5373c966d1f4eb9a; create temporary table __temp__country se...
Read more

twig - Using Twigbridge in a Laravel 5.1 Package -

i'm trying create laravel 5.1 package uses twigbridge instead of .php views. can normal .php views display fine, when try make use of .twig templates i'm met error. possible use twigbridge templates when creating views laravel package or pretty stuck blade , php ? edit 1: loading twig template without extending works. it's when start using {% extends 'file' %} error comes out. i error error loading /virtual/laravel/packages/username/mypackage/src/views/sample.twig: template "templates.master" not defined () in "/virtual/laravel/packages/username/mypackage/src/views/sample.twig" @ line 1. my folders username |_ mypackage |_ src |_ controllers - samplecontroller.php |_ views |_ templates - master.twig - sample.twig twig template sample.twig {% extends 'templates.master' %} {% block content %} {{ parent() ...
Read more

jdbc - Not able to establish database connection in eclipse -

i want make new database connection (db2) in eclipse purpose of using jpa. in jpa perspective, in data source explorer view, when try create new db connection, receive following logs when try ping server. org.eclipse.datatools.connectivity.exceptions.dbnotstartexception: no start database command issued. errorcode = -4499, sqlstate = 08001. @ org.eclipse.datatools.enablement.ibm.db2.internal.luw.jdbcluwjdbcconnection.getconnectexception(jdbcluwjdbcconnection.java:74) @ org.eclipse.datatools.connectivity.ui.pingjob.gettestconnectionexception(pingjob.java:81) @ org.eclipse.datatools.connectivity.ui.pingjob.run(pingjob.java:63) @ org.eclipse.core.internal.jobs.worker.run(worker.java:54) caused by: com.ibm.db2.jcc.am.ro: [jcc][t4][2043][11550][4.8.87] exception java.net.connectexception: error opening socket server example.example.com/51.37.93.117 on port 50,000 message: connection timed out: connect. errorcode=-4499, sqlstate=08001 @ com.ibm.db2.jcc.am.gd.a(gd.j...
Read more