"ssh -v" should print debug info to stderr, at least if you are using OpenSSH. If you run it in a normal terminal (including Windows Terminal, if you're connecting from Windows 10/11), you should see a bunch of extra output showing you what's going on with the SSH connection. Be careful to check there's no sensitive info in the output if you are sharing it (public keys are generally not a problem). There's quite a bit of noise in the debugging, and some errors are not really errors (like "No such file or directory" errors for optional files). Here's the first few lines of it, connecting from W11 to a Pi (other than versions and paths, OpenSSH is the basically the same for Linux, Windows, and macOS):To be honest, I didn't understand ssh -v. I launched a console and ran this command but didn't see any difference. Is there a log ?
Code:
PowerShell 7.4.5PS C:\Users\Murph> ssh -v raspberrypiOpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disablingdebug1: Connecting to raspberrypi [2001:db8:af2e:485:4309:5d22:fb9c:9138] port 22.debug1: Connection established.debug1: identity file C:\\Users\\Murph/.ssh/id_rsa type 0debug1: identity file C:\\Users\\Murph/.ssh/id_rsa-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_dsa type -1debug1: identity file C:\\Users\\Murph/.ssh/id_dsa-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ecdsa type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ecdsa-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ecdsa_sk type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ecdsa_sk-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ed25519 type 3debug1: identity file C:\\Users\\Murph/.ssh/id_ed25519-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ed25519_sk type -1debug1: identity file C:\\Users\\Murph/.ssh/id_ed25519_sk-cert type -1debug1: identity file C:\\Users\\Murph/.ssh/id_xmss type -1debug1: identity file C:\\Users\\Murph/.ssh/id_xmss-cert type -1debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.6debug1: Remote protocol version 2.0, remote software version OpenSSH_9.2p1 Debian-2+deb12u3debug1: compat_banner: match: OpenSSH_9.2p1 Debian-2+deb12u3 pat OpenSSH* compat 0x04000000debug1: Authenticating to raspberrypi:22 as 'murph'…It doesn't look like you are out of memory or swap in that htop snapshot. There's a bit of load, that's expected with what you are running, doesn't look excessive or overloaded in terms of CPU usage. Number of processes and threads is quite low (low is usually a good thing, it means you don't have something spawning processes or threads like crazy and causing a problem that way). It basically looks like a normal, healthy system at that moment in time.
Statistics: Posted by Murph9000 — Wed Oct 02, 2024 1:21 am