MobileRead Forums - View Single Post

knc1 · 04-13-2012, 01:42 PM

Try adding the debug flag(s) to your ssh command.

If using the command line, then: ssh -vv <whatever>
If using Putty, then Putty should have a debug flag(s) option somewhere.

The "connection refused" is a general purpose result message, designed not to give away the reason for the failure.
Most often the cause is the sshd daemon isn't running on the target device or port 22 is firewalled somewhere.

Changing keys will not solve this, it is failing long before any keys become involved in the handshake process.

The "normal" (meaning, a standard Linux or *nix installation) location for the connection log messages is /var/log/auth.log but I do not know if your Kindle uses that "normal" name and path for the log.

04-13-2012, 01:42 PM	#2
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Try adding the debug flag(s) to your ssh command. If using the command line, then: ssh -vv <whatever> If using Putty, then Putty should have a debug flag(s) option somewhere. The "connection refused" is a general purpose result message, designed not to give away the reason for the failure. Most often the cause is the sshd daemon isn't running on the target device or port 22 is firewalled somewhere. Changing keys will not solve this, it is failing long before any keys become involved in the handshake process. The "normal" (meaning, a standard Linux or *nix installation) location for the connection log messages is /var/log/auth.log but I do not know if your Kindle uses that "normal" name and path for the log.